Fails to import access database in SAS Enterprise Guide 7.1

[GDumont]

Hi all,

I'm trying to import an access database by the "proc import" procedure and also by point-click, but my attempts are failing.

When I try by "proc import", the log shows the messages:

"ERROR: Connect: Class not registered" and "ERROR: Error in the LIBNAME statement."

When I try by point-click, the following error is being shown:

"A problem was encountered while attempting to use OLEDB to read data from the source file.

This may be caused due to the source file being opened within another application or a security issue while attempting to access the source file.

Because of this problem the Import Data wizard is unable to continue."

I also tried putting the access file on my computer's local server but it didn't make any difference

I searched here on the SAS Community and found that this error may be due to the difference between SAS Enterprise Guide and Microsoft Office being installed on different "bit" platforms (32-bits and 64-bits). But in my case both are installed as 64-bit.

Unfortunately, I am not able to get around this situation. Can anybody help me?

[SASKiwi]

Please post your complete PROC IMPORT SAS log. Is this a first-time attempt or was it working and now it isn't? 

[GDumont]

Thanks for your response.

It is a simple PROC IMPORT procedure. Even if I try by point-and-click ("File" > "Import Data" > "Open" > "Next"), SAS gives the second error reported in the topic (OLEDB error).

proc import dbms=access out=&&bases&i replace
    datatable=&&bases&i;                      
    database="C:\Users\gza001\Documents\ARQ.MDB"; 
run;

[SASKiwi]

Are you using a remote SAS server? If so then the setup for MS Access needs to be on that server, not your PC.

Is this the first time you have tried this or was it working before?

[GDumont]

Even when I put the file on my desktop the same error appears. Was that your question?

[jebjur]

Here is a good SAS note for the CONNECT: Class Not Registered error. http://support.sas.com/kb/63750

It might be a better idea to open a track with Technical Support for assistance with these issues