Importing from Excel to Access 2003

[Dave Z]

A user of mine recently got a new machine (with an upgrade to Access 2003
from 2000). He's going through his usual import procedure (File >> Get
External Data >> Import). He drills down on the spreadsheets he wants to
import, clicks Import and gets a message saying:

The Microsoft Jet database engine could not find the object 'Databases'

Using my machine with Access 2003, I'm able to import the data from these
spreadsheets with no problem. This leads me to believe there's a problem
with his Access. Has anyone seen this behavior? Any advice is much
appreciated....

 

[Klatuu]

This is most likely a VBA reference issue. The Object Libraries for 2003 are
different than 2000. Open the VBA editor, click Tools->References. Look for
any that are marked "Missing". If this user is using a shared front end, you
will need to install his own version of the mdb and set the references for
2003 Object Libraries.

 

[Dave Z]

I'm in Visual Basic Editor right now looking at the Available References. I
see that the Microsoft Access 11.0 Object Library is checked along with the
ActiveX Data Objects 2.1 Library. There are a slew of other libraries that
are unchecked. Is this where I should be looking? I'm not sure what you
mean by any that are marked "missing."

 

[Klatuu]

You will also need Microsoft Excel 11.0. 11.0 is for 2003, For 2000 they
will be 9.0

 

[Dave Z]

Okay, I've checked the Excel 11.0 Object Library and closed VBA Editor but
I'm still getting the same Jet Database error when I try to run the import.
Weird thing is I don't have this Excel Object Library checked on MY version
of Access and I'm able to import Excel data without getting that error.
We're both running version 11.6355.6408 (SP1).

 

[Klatuu]

How about Microsoft DAO 3.6 Object Library? Do you have that one?

 

[Dave Z]

Neither of us have that one checked.

How about Microsoft DAO 3.6 Object Library? Do you have that one?

 

[Klatuu]

I think you need it.

Neither of us have that one checked.

 

[Dave Z]

Okay, I checked the Microsoft DAO 3.6 Object Library on his machine and I'm
still getting that error. The DAO is unchecked on my machine and I'm able to
import from Excel with no problems so I don't think this particular object is
the issue.

One thing that I've noticed when I try to import from Excel on his Access is
once I select his spreadsheet (1 Underframe Front and Left FH 7-19-05.xls)
the error says:

The Microsoft Jet database engine could not find the object "1 Underframe
Front and Left FH 7-19-05$". Make sure the object exists and that you spell
its name and the path name correctly.

Don't know if that dollar sign has anything to do with it or if the file
name is too long? Works just fine on my computer. Please advise.

 

[Klatuu]

I don't know if I can help any more. If it is not a reference problem, then
I am a bit lost. I don't know that the $ is a problem, but in a case like
this, I would change the name and try it to see what happens.

 

[Dave Z]

I'll give that a try. Is there anyone else there who can help?

 

[G. Vaught]

Did your friend get the entire Office 2003 Professional or just Access 2003
upgraded. He may need to reinstall Office 2003/Access 2033 and ensure the
Custom install has been used. If you do a typical install, which most
computer companies will do regardless, you won't get all the necessary
wizards and additional import/export file formats.