Access 97 does not want to import Excel anymore after installing Office XP/2003 (Standard or Professional)or,Access 97 gives "Couldn't find installable ISAM" error when using in conjunction with Office XP or Office 2003 on the same machine (importing Excel)Description of problem:1. Access 97 gives a "Couldn't find installable ISAM" error when importing/exporting your data from Excel to Access because of lost links in the registration of required DLL’s for Access 97, 2. Spreadsheet files (i.e. Excel, Lotus) cannot be imported into Access 97 even though it has been working perfectly prior to Office XP or 2003 being installed on a machine. 3. The Access 97 database that fails to import Excel, can be of *.MDB or *.MDE type and will suddenly fail even though nothing in the actual database or code has been changed. Actual problem: When installing Access 97 in conjunction with MS Office XP or 2003 (or the other way round), on any Windows machine the registration of some or all the .dll files required for ISAM (indexed sequential access method) that Access 97 uses as part of DAO, isn’t done or gets deleted because they are not required in Office 2003. The problem will occur even if you only install Office 2003 Standard that does not have Access included at all in the package (Office 2003 Professional does). This problem will also occur irrespective of whether Access 97 was loaded prior to or after the installation of Office XP/2003. Reinstalling either Access 97 or Office 2003 (in any particular order) will not help. Solution:You have to manually re-register the required DLLs:1. Click Start > Run. Depending on your operating system, copy and paste each of the commands into the RUN Command Line (Start, Run) and execute them (its only the Windows paths that vary for the different operating systems).
Win 95/98 regsvr32 "c:\Windows\System\msexcl35.dll" regsvr32 "c:\Windows\System\mstext35.dll"
WinNT regsvr32 "c:\Winnt\System32\msexcl35.dll" regsvr32 "c:\Winnt\System32\mstext35.dll"
Win2000 regsvr32 "c:\ Winnt \System\msexcl35.dll" regsvr32 "c:\ Winnt \System\mstext35.dll"
WinXP regsvr32 "c:\Windows\System32\msexcl35.dll" regsvr32 "c:\Windows\System32\mstext35.dll"
N.B. It must give a "Success" message after executing each of these commands, otherwise the registration of the .dll was not performed correctly. If you cannot find the above .dll's in the folders noted above, you may want to search your computer for the files and modify the paths in the above commands accordingly.
2. Quit Access 97 and then load your Access 97 database and recompile all modules. (Go into the Form that imports the data, click Design and click the Code icon so that you can see the visual basic code. On Tools click "Compile all modules". Save all. Problem should be solved!
3. It is better to Reboot with these things
4. You unfortunately have to repeat these instructions on every computer experiencing this problem (if you are a “baby boomer” you will probably still know how to use a MS-Dos batch file to auto-run these! The generation “Y”’s have to do it manually! Ha-ha!)
Note: I am not sure if the registration of the Access 97 .dll's can influence the correct functioning of Office 2003 in any way, but so far I have not experienced any problems. Please send me a quick email if this information has solved your problem! Christiaan Mostert, South Africa
|