I have a script-heavy Access db that I recently sent out to the end-users for bug testing. The scripts mainly read data, add/update/remove from internal tables, and interact with a shared drive.
They came back immediately with a report that the most important part can’t run due to a missing/broken reference to ‘msado15.dll’ version 6.1 (aka Microsoft ActiveX Data Objects 6.1 Library). This brings 2 questions:
-
Why would this library exist on my machine but not on theirs? As far as I know, all our machines had the same standard Office install package. Is it because I have SQL Server and they don’t?
-
I think I’ve found an alternative, msado28.tlb (aka Microsoft ActiveX Data Objects 2.8 Library), which seems to work just as well, but I haven’t tested on the user’s machines. Is this a good substitute?
Do you need the library in the distributed version? You could use late binding:
It is usually easiest to develop with early binding and distribute with late binding.