Importing an Excel file is not an option in Get External Data

[dana803]

I have a user who is running Windows 98 and Office 97 Pro. He has an Excel spreadsheet he wants to import into Access. When he goes to File..Get External Data, the xls file type is not an option in the field to specify file type. I have uninstalled and reinstalled Office. When I'm in custom setup in the Data Access options, the box next to the Excel driver is grayed out and the word Installed appears to the right of it. I have the same programs on my computer, but I don't have this problem. I have a lot more file type options than he does. I even installed the Data Access stuff from the Valupak folder on the CD. How can I fix this?

 

[jjlogan]

Our group had this problem too. Some of us had both Access 97 and Access 2000 installed on our PC concurrently. I think the problem went away when we uninstalled one version (we happened to get rid of version 97). The problem was caused by the both versions sharing the Spreadsheet Import Wizard.

Jeff

 

[Badly]

Hi Dana803! Try this:

1. run Office setup > add/remove

2. select 'data access' and 'change option'

3. select 'database drivers' and 'change option'

4. note which ones are greyed out and exit setup

5. in C:\Windows\System, rename the files as needed

for Excel driver rename MSEXCEL35.DLL to MSEXCEL35.DL_

for Text driver rename MSTEXT35.DLL to MSTEXT35.DL_

for Dbase driver rename rename MSXBSE35.DLL to MSXBSE35.DL_

6. repeat steps 1, 2, 3 and you should now be able to clear and reinstall the drivers in setup. This will replace the appropriate DLL files and should sort it out. Don't know the exact cause, probably DLL corruption or a registry error of some kind.

Badly

 

[Badly]

Hi again

Addition to the above, when you go to rename any of the files above you'll probably see a newer version i.e.

MSEXCEL35.DLL (this is the Office97 Jet version 3.5nn)
MSEXCEL40.DLL (this is a newer Jet version 4.0nn)

It seems that newer versions of the DLL's have been loaded by a.n.other application and probably caused the registry confusion. So far I haven't found any problems with 'refreshing' the version 3.5 info as above but worth keeping in mind that the newer version may be needed by something else installed on the pc.

Badly

 

[Rich76]

I had the same issue and the Badly method fixed it. Thanks!!