Hardware, software, and user requirement details
Hardware
See specifications outlined by Microsoft for your version of Windows.
Windows operating systems supported
Connexion client 3.X is supported for use with the 64-bit version of Microsoft Windows 10, version 1803 or newer.
Caution: Connexion client 3.X is not compatible with versions of Microsoft Office that are no longer supported by Microsoft. 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.X, but instead continue to use version 2.63.
Disk space
Minimum hard-disk space required for the Connexion client: 4 GB RAM
User-level requirements for installing
Logon with local administrator-level privileges is either required or highly recommended for installing the client as noted in the following list of circumstances:
- Required if you use Windows 10 - For these operating systems, you must log on with administrator-level privileges to install any software program.
Note: If you have Windows 10, after you save the download file, right-click the *.exe installation file, and click Run as administrator to help prevent possible problems with installing.
Internet connection required for some functions
An internet connection is required for the following functions.
| Function | Description |
|---|---|
| Client log on | You must have a TCP/IP Internet connection to log on to the OCLC system from the client. You can use these access methods:
For more information, see Set up communications and log on. |
| Offline record validation | Although you do not need to be logged on to the OCLC system to validate records offline, your workstation must have Internet access for validation to work when you are offline. |
| Automatically transliterating Arabic script in Arabic or Persian records while offline | An Internet connection is required to use Edit > Transliterate > Arabic [or Persian] to transliterate existing romanized data (Latin-script-equivalent data) in records to equivalent Arabic script data. |
Fonts for printing records and labels
- The client default font for printing records and lists is either the Arial Unicode MS font, if it is installed, or the default Windows font on your workstation.
- OCLC recommends that you have the Arial Unicode MS font installed on your workstation for access to the set of diacritics and special characters adopted by the American Library Association (ALA) for use in Latin script MARC records.
- This font is included with many Microsoft applications, but it may not be automatically installed with these Microsoft applications. For installation instructions, run one of the Microsoft applications such as Word. Navigate to Help (Start > Help [or Help and Support]) and search for Arial Unicode MS. Other Unicode-based fonts may also work in the client.
- The client default font for printing labels is the ALA BT Courier font, which is installed with the client software. OCLC recommends this font for printing labels.
- Font settings for printing records, lists, and labels are in Tools > Options > Fonts.
Notes for macro users who have newer versions of Windows
If you have Windows 7/8/8.1 Professional (64-bit) or Windows 7 Enterprise (32- bit) or other newer versions, you may need to move your \macro directory after upgrading or installing version 2.50 of the client.
In previous versions of the Client, Windows may have stored your macros in a Virtual Store. The Virtual Store is something Microsoft created to allow backward compatibility for old applications that need to write to the Program Files directory. With Vista, Microsoft stopped allowing Standard User-level users to write anything under the Program Files directory. When the Connexion client tries to write to the \Macros directory, Windows writes the data to the following directory instead, for example: X:\Users\<username>\AppData\Default (or Local)\VirtualStore\Program Files(x86)\OCLC\Connexion\Macros, where X is the letter of your hard drive.
Connexion client 2.50 has included an application manifest which informs the Windows operating system what permission level the client needs. The value is set to Highest Available to allow the highest access level possible without requiring Administrator privileges. Inclusion of this manifest also disables the use of the Virtual Store. If you edited macros in previous versions of the client, those changes will not be visible in version 2.50 until you copy them from the Virtual Store back to X:\Program Files\OCLC\Connexion\Program\Macros:
- With the Connexion client closed, navigate to your Virtual Store using Windows Explorer. This may be a slightly different location depending on what version of Windows you are running (and whether it is 32-bit or 64-bit), but the location will be something like one of the following:
- Press and hold Ctrl while you select all of the *.mbk files within that directory (except the OCLC.mbk and the Dewey.mbk files, which are OCLC-provided macro books).
- Press Ctrl+C to copy them.
- Navigate to the \Macros directory created by the Connexion Client installation (for example, X:\Program Files\OCLC\Connexion\Program\Macros).
- Press Ctrl+V to paste the macro books to this directory.
- Open the Connexion Client and navigate to Tools > Macros > Manage. Your macro books should now be listed and available for use in the Macro window.
In addition, non-Administrator-level users may not have permission to write to the X:\Program Files\OCLC\Connexion\Program\Macros directory. If this is the case, change the security permissions to allow write privileges:
- Open Windows Explorer, navigate to X:\Program Files\OCLC\Connexion\ Program\Macros, and right-click the \Macros folder.
- On the pop-up menu, click Sharing and Security > Security.
- In the Group or user name list, highlight the user you want to change.
- In the Permissions... list, select the Allow check box for Full Control.
- Click OK to save the setting.