Importing a .mdb file into SAS with "SAS/ACCESS Interface to PC Files" but without PC FIles Server

[AndrewJones]

Hello,  We have recently had SAS Office Analytics installed on a Windows server, which means that we now have "SAS/ACCESS Interface to PC Files" installed, but we don't have the PC Files server installed (don't ask me why - I wasn't involved in the installation).  I was trying to import data from a .mdb using SAS EG 7.15, but when I try the following code

proc import datatable="vehicle_details" dbms=access out=code44 replace;
		database="\\server\code44.mdb";
run;

libname code44 "\\server\code44.mdb";

I get the error message 'ERROR: Connect: Class not registered'.  I believe I get this because the PC Files server is not installed.

Is there is a way of importing .mdb file into SAS without PC Files Server and if so, how?  Or do we need to install PC Files Server.  I know that the SAS version is 64bit and the Microsoft Office drivers are 32bit.  Is this the issue?

Thanks

Andrew

[Kurt_Bremser]

Have you already worked through the flowchart found here: http://support.sas.com/kb/60/356.html?

[AndrewJones]

Thanks for the reply.  Yes, I did, which is why I believe that I need to either install the PC Files Server or change the drivers, but I was hoping that there was a simple programming solution, rather than relying on other people to make changes for me.  The page is over a year old, so I hoped that there was now a different solution.

[Kurt_Bremser]

This page is the authoritative source for fixing your problem. What did you find when you worked through it? Bitness mismatch, missing ACE?

Have you made sure ACCESS to PC Files is actually installed and licensed (proc product_status, proc setinit)?

[Kurt_Bremser · Accepted solution]

Note that, while xlsx is an openly documented format for which anybody can (legally) write an interface nowadays (and SAS has done exactly that), .mdb files have a proprietary format for which you need a module supplied by Microsoft to access them, and that has to match the software that uses it in terms of bitness. It's also only available on Windows.

[AndrewJones]

It was a bitness mismatch.  Thanks for the replies, I now know that my hope was in vain and I will need to get the IT dept to makes some changes.