[AccessD] msado15.dll

Just a guess, but did he unregister the old one first?  When Microsoft
decided to stop changing the name of that dll with each version change
they seem to have created a bear trap.  It's possible that trying to
register a newer version only works if you unregister the old version
first.  HOWEVER, do you know if he has any apps that rely on the earlier
version and hold onto it?

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Tuesday, April 21, 2009 9:23 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] msado15.dll

Dear List:

In the further adventures of the cockeyed references:

In our last episode, the legacy 2003 app I'm working on could be
converted from mdb to accdb but not compiled because of a references
problem.  Well, we got that straightened out.  It had to do with the
order of the references.  We can apparently live without the DAO
reference because (I'm
guessing) the Microsoft Office 12.0 Access database engine Object takes
care of all that.

FYI here are the references and the order in which they allowed the
compile to complete successfully:

Visual Basic for Applications
MS Access 12.0 Object Library
MS Office 12.0 Access Database Engine Object OLE Automation MS Calendar
Control 2007 MS Word 12.0 Object Library MS Visual Basic for
Applications Extensibility 5.3

This order also resolved the compile problem of fld.Name where fld was
Dimmed as Field.

Now client has a problem creating an accde from this accdb. When he
creates the accde he gets a rather elaborate message from Access with
this "Your Microsoft Office Access database or project contains a
missing or broken reference to the file 'msado15.dll' version 6.0.
However he clicks OK,the accde is created, and it appears to run OK
although not all functions in the accde have been tested. 

The client writes to me:"I Googled 'msado15.dll' like you suggest, and
find I have it and so I register it like Microsoft says and the
registration is successful.  So I try to create accde and still get msg,
but note it says 'msado15.dll' version 6.  I have v. 2.81.1132.0 and
cannot find a v.6 anywhere online.  What version do you have?  If you
have v.6, would you email it to me?"

So I did mail my version 6 to him.  And he overwrote the old one and
registered it.  Now it gets even weirder.  He writes :" I deleted the
msado15.dll altogether and after a few seconds, it magically
re-appeared, in the old version 2.81.1132.0.  This is getting too weird
for me.".

Does anyone have a theory about why he's getting this reference message
and why he can't get version 6 to stay put?.  

BTW, in the references dialog box no references are tagged as Missing,
and the application compiles without an error.

MTIA

Rocky

 


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com