Skip to main content
OCLC Support

Connexion client known issues

Find known issues for the Connexion client.
Issue Details

Running multiple Connexion windows at the same time

Due to the update to 64-bit, multiple instances of Connexion Client cannot run at the same time. 

Workaround: Using the View > Pinned menu option within Connexion Client when looking at multiple records at a time or using a virtual machine to run multiple instances of Connexion Client at one time.   

Help icon in the Connexion macro editor is no longer supported

In the Connexion macro editor and debugger, there is a question mark icon that would previously take users to macro-specific help.  This icon utilized a feature that is no longer supported by Microsoft.  Due to the nature of the language used to code the macro editor, we are unable to remove this icon from the user interface.

Workaround: There are two additional options for getting to the macro help: 

  1. Press the F1 key on your keyboard 

  1. Click on the Help menu above the toolbar, and then click Macro Help 

Both options will take you to the OCLC Macro support site. 

Client 3.0 is not compatible with unsupported versions of Microsoft Office

Connexion client 3.0 is not compatible with versions of Microsoft Office that are no longer supported by Microsoft. 

Workaround: If you are using an older, 32-bit version of Microsoft Office that is out of support, we suggest that you either upgrade your Microsoft Office to a newer, supported version; or, that you do not upgrade to Connexion client 3.0, but instead continue to use version 2.63. 
OCLC Gateway export destination no longer works after upgrading Connexion client

If you set up an OCLC Gateway export destination in a previous version of the client, export may not behave as expected after you upgrade to Client 3.0.
Workaround: Check or reset options.
  1. Navigate to Tools > Options > Export.
  2. From the Export tab, select OCLC Gateway export from the Destinations list and then click Edit.
  3. From the OCLC Gateway Export - Local System Settings window, check and correct settings if needed.
250 field in Constant Data overwrites existing 250 field when applied

The client does not recognize that the 250 field is repeatable. As a result, a 250 field in a constant data record will overwrite an existing 250 field when constant data is applied to a bibliographic record.
Workaround: Enter the text you want to add to the 250 field in a tag that is not often used, and then change the tag number to 250 after you apply constant data.
MARCXML record export from online save file generates an error

If you are configured to export records in MARCXML, you will receive the following error message when attempting to export a single record from the online save file: Unable to cast object of type 'ConnexionUISchema.CDFRecType1' to type 'ConnexionUISchema.CDFRecType’
Workaround: To avoid receiving an error message:
  • Use the local save file to export records
  • Use batch export if exporting from the online save file
Persian transliteration issues

The Persian transliterator:
  • Treats the romanized "th" as one character, Theh 062B. It should be treated as two characters, Teh 062A and Heh 0647.
  • Does not transliterate characters following the romanized miagkii znak (prime mark) correctly.
Cannot access Connexion-client-specific macro commands from the OCLC Connexion Macro Editor and Debugger window

The Help button (OCLC Connexion Macro Editor and Debugger window - Help button) in the OCLC Connexion Macro Editor and Debugger window does not work and cannot be fixed. See Use macros for help with macros.
Cannot maximize (re-display) Connexion client from a minimized position in the task bar

When you minimize the Connexion client, it becomes an icon in the task bar on your desktop, and you should be able to maximize/restore (redisplay) it by clicking the icon. If you are unable to maximize the client from the task bar icon, use one of the following workarounds.
Workaround: Click the Connexion client icon in the task bar, and then press and hold the Windows key (Windows key) on your keyboard while you click the <Up arrow> key or use Shift+Ctrl and right-click on the icon, then click Restore.
Updating holdings on records imported into the client via Z39.50 (Tools menu) does not work

If you use Update Holdings to add a Z39.50-retrieved local system record to WorldCat (the client imports the record as a workform), you receive a message that field 001 is missing the OCLC number. As a workform, the record should not have an OCLC number in field 001. This is a system error.
Workaround: Derive a new record from the Z39.50 imported record and then add to WorldCat using Update Holdings.
If you do not uninstall the client before upgrading, changing the "Install for everyone or just for you" setting during upgrade makes the client inoperable
 Note: OCLC recommends uninstalling before you upgrade to prevent possible problems like this one.
When you upgrade the client without first uninstalling, in the window where you select an option to install for everyone who uses the workstation or just for you, you must select the same option you selected during your original installation. If you don't and the client becomes inoperable, you must uninstall and re-install the new version.

To determine which selection you made for the original client installation, check the location of the OCLC Connexion client desktop shortcut:
  • If you selected installation for you only, OCLC Connexion Client is listed in X:\Documents and Settings\[your username]\Desktop, where X = the letter of your hard drive.
  • If you selected installation for everyone, OCLC Connexion Client is listed in X:\Documents and Settings\All Users\Desktop.
The first time you display a WorldCat record using a new user profile, the record window is not maximized in the client window

The first WorldCat record displayed using a new user profile is a truncated view in the upper left part of the work area in the client window. To maximize the record window, use Window, Tile Vertically or Tile Horizontally.
For online constant data (CD) only, diacritics and special characters in CD name and CD My Status cause errors

Has been added as a Caution to client documentation and Help in the same topic specified in the known problem directly above. The cautionary note has a list of the characters that cause errors.
MARC-8 Characters Verify no longer highlights non-MARC-8 characters

If you put characters that are outside of the MARC-8 character set into a record and perform the MARC-8 Characters Verify command, the change to accepting all Unicode characters prevents this function from isolating characters that are not part of the MARC-8 character set.
Searches using characters above Unicode Plane Zero return incorrect results

Connexion client is currently unable to send the correct characters if characters entered are above the basic multilingual plane (BMP). The client handles Unicode characters in the BMP, which contains characters with a code point between U+0000 and U+FFFF. The BMP includes all the characters originally supported for cataloging in addition to many more. However, some language characters are found using supplementary planes and code points, such as CJK Unified Ideographs Extension B which has characters between U+20000 and U+2A6DF.
  • In the client, change search argument to use only MARC-8 characters, could be switching to a name or subject that is all MARC-8 instead of what was originally entered.
  • Use Record Manager.
CJK E-Dictionary search results are incomplete

When you use the E-Dictionary Search window (that is, click Tools > CJK E-Dictionary, enter an input code or character in the search box, select an input method and a script, and click Find), the E-Dictionary Search Results window shows only the EACC data in the first column. The other columns are missing data.
Workaround: In the E-Dictionary Search Results window, double-click the EACC entry. The E-Dictionary Entry window opens, showing all of the codes that are supposed to display in the search results.


  • Was this article helpful?