Missing reference msador15.dll version 2.8

  • Thread starter Thread starter SG
  • Start date Start date
S

SG

Hi,

I developed database on my computer, everything is fine. But when run this
access database from other computer, it complains about missing reference
msador15.dll version 2.8. Those computers have the same version of officexp,
don't understand why this happens.

Please help.
Thanks,
Sarah
 
Office XP did not include ADO 2.8, that version has been installed on your
PC by something else. You could install the latest version of MDAC on the
target PC to bring it up to 2.8 (MDAC can be downloaded from Microsoft's web
site). However, you probably shouldn't be using that particular object
library, anyway - it's a cut-down version of the ADO object library designed
for use in web pages. The main ADO object library (msado2x.tlb, 'Microsoft
ActiveX Data Objects 2.x Library') is more suitable for use in an Access
application.
 
Hi Brendan,

Thanks for your quick response. I did what you suggested that intead of
using ADO2.8, I chose msado2.x.tlb, but the similiar complaint appears
still. This time it complains about msado2x.tlb, I'm using 2.7, is that
because the version is too new?

Please advice,
Thanks,
Sarah
 
You need to either update the target PC to the latest version (2.8) *or* use
a version that is already installed on the target PC. There are many
applications that install different versions of MDAC, so it is not possible
for me to predict what versions of the msado2.x library may be installed on
the target PC. You can find out by opening the VBA editor on the target PC
and going to Tools, References and checking the versions that are listed
there. You could simply change the reference on the target PC, and that
should fix the problem for now, but it would be likely to occur again the
next time you copy an updated version from your development PC.
Alternatively, you can change the reference on your development PC to be the
same as one of the versions on the target PC. Or, and this is my personal
preference, forget ADO and stick with DAO. There are far fewer versions of
DAO to worry about.
 
Back
Top