Solved

Could Not Find Installable ISAM

Posted on 2013-06-24
3
790 Views
Last Modified: 2013-06-25
In Access 2002 I'm tryng to use VBA to link to SQL Server.

DoCmd.TransferDatabase acLink, "ODBC Database", "DRIVER={SQL Server};Server=SERVERNAME;Database=DBNAME;Trusted_Connection=yes;", acTable, strSourceObject, strTargetObject, , True

SERVERNAME andDBName in my cod are valid SQL Sever objects.
strSourceObject and strTargetObject arethe source and target table names.

I got the "Cannot find installable ISAM" error. In researching this I looked at my registry where severa keys point to the various DLLs required to solve this issue. I copied all of the following DLLS to the C:\Program Files\Microsoft Office\Office10\ folder becaus that isthe folder the registry is poining to:

Msexcl40.dll
Msexch40.dll
Msrd2x40.dll
Msrd3x40.dll
Msltus40.dll
Mspbde40.dll
Mstext40.dll
Msxbde40.dll

I still got the error. One final not my Access 2002 ia installed on a windows XP box that has Outook 2010 and Excel and Wor 2007 -  a real mismash!

The only thing I can think of it to re-register the dlls from the command line with, for example:

regsvr32  C:\Program Files\Microsoft Office\Office10\Msexcl40.dll
0
Comment
Question by:paulmcneil
  • 2
3 Comments
 
LVL 84

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 500 total points
Comment Utility
I copied all of the following DLLS to the C:\Program Files\Microsoft Office\Office10\ folder
You really, really should not do this. I'd suggest that you reinstall Office at this point to insure that you have the correct versions of all your dependency files.

Also make sure that you're fully up to date on all Office/Access and Windows updates.
0
 
LVL 11

Expert Comment

by:datAdrenaline
Comment Utility
I do agree with LMS, you don't (and should not) to anything with all those DLL's ... and if you did, then a removal of those DLL and a reinstall of Office is likely appropriate.

---

... Plus ...

The issue you are experiencing is easy to solve.  You simply need to add "ODBC;" to the beginning of your connection string ...

DoCmd.TransferDatabase acLink, "ODBC Database", "ODBC;DRIVER={SQL Server};Server=SERVERNAME;Database=DBNAME;Trusted_Connection=yes;", acTable, strSourceObject, strTargetObject, , True
0
 
LVL 11

Expert Comment

by:datAdrenaline
Comment Utility
While you have accepted an answer (glad it got you going!) please do note that your Connect string will indeed need the ODBC prepended to it as I have shown, otherwise you will continue to get the error of "Cannot find installable ISAM".
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

Today's users almost expect this to happen in all search boxes. After all, if their favourite search engine juggles with tens of thousand keywords while they type, and suggests matching phrases on the fly, why shouldn't they expect the same from you…
Regardless of which version on MS Access you are using, one of the harder data-entry forms to create is one where most data from previous entries needs to be appended to new records, especially when there are numerous fields and records involved.  W…
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database. Split up all multi-value fields into single values: Split up fields that belong to other things into separate tables: Make sure that all record…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now