For information about the installation, administration, and usage of SAS PC Files Server, see the " Quick Start for Installation" section in SAS ® 9.4 PC Files Server: Installation and Configuration Guide, Second Edition. In this situation, you must use the PC Files Server to bridge the architecture mismatch. So, if your Office package is 32-bit, the 32-bit runtime package is required, which still causes an error if you have 64-bit SAS due to the architecture mismatch. However, the bitness of the runtime package must match the bitness of the installed Office package. If you can, you should match the bitness of the runtime package to the bitness of SAS. You can download the runtime package directly from Microsoft.
You can install the Microsoft ACE components independently from Microsoft Office as part of the Microsoft Acess 2013 Runtime package. For details about these two identifiers and syntax examples, see the " Import and Export Microsoft Excel Files Using the XLS and XLSX Identifiers" section in SAS/ACCESS ® 9.4 Interface to PC Files: Reference, Fourth Edition. Or, you can use the DBMS=XLS identifier with PROC IMPORT and PROC EXPORT. You can use the DBMS=XLSX identifier with the IMPORT or EXPORT procedures and a LIBNAME statement (depending on your SAS release). If you are working with Microsoft Excel data, you can use one of the two SAS DBMS identifiers that have no dependency on the Microsoft ACE components. Note: Option 3 is the recommended option.
For Microsoft Access connectivity, see Option 3 or Option 4.For Microsoft Excel connectivity, see Option 1 or Option 3.If you have 64-Bit SAS installed with 32-Bit Microsoft Office, you have the following options: For Microsoft Access connectivity, see Option 4.For Microsoft Excel connectivity, see Option 1 or Option 4.If you have 32-Bit SAS installed with 64-Bit Microsoft Office, you have the following options: For Microsoft Access connectivity, see Option 2.For Microsoft Excel connectivity, see Option 1 or Option 2.If Microsoft ACE is missing, you have the following options:
This SAS Note describes options that you have to work around this driver issue for these scenarios: Microsoft ACE is missing, 32-Bit SAS is installed with 64-Bit Microsoft Office, and 64-Bit SAS is installed with 32-Bit Microsoft Office.
64-bit applications cannot use 32-bit drivers and vice versa. The driver might not be found for a few reasons, such as being missing entirely or being installed at a different bit architecture. If the required driver is not found, the " Connect: Class not registered" error message is returned to the SAS log. SAS software requires you to use the Microsoft Access Connectivity Engine (ACE) for connectivity to files types such as Microsoft Excel and Microsoft Access when using certain database management system (DBMS) engines.