> Your explanation on how to resolve this problem is helpful.
Thank You. This was not evident from your initial reply.
> However, I would like to know what is happening behind the scenes. Why
> did my code work fine in the first database but no longer works in the new copy?
Is the same PC being used in both cases? If the path to the DAO library is
different on two different computers, this could account for a MISSING
reference error. Sometimes, a reference can even be missing without being
flagged as such. Refreshing the references collection tends to fix that
error. Doug Steele talks about this in his article (see below). Without
having both copies of your database available to look at, it's hard to offer
you any definitive reasons for such an error. Have you read the references
articles by Access MVP's Doug Steele and Allen Browne? If not, I recommend
that you read and bookmark both of these articles:
Solving Problems with Library References (Allen Browne)
http://allenbrowne.com/ser-38.html
Access Reference Problems (Doug Steele)
http://www.accessmvp.com/djsteele/Ac...nceErrors.html
> What is the reason for changing the references in the Microsoft DAO 3.51 Object Library?
What changed, exactly? Are you seeing a MISSING reference error? Other
possibilities include misspelling "Database" in code or perhaps having a
declaration line that is outside a procedure, but not within the Declarations
section of the module.
You indicated Access 97. While you did not indicate a later version of
Access, I can tell you that if you attempted to import all objects from your
JET 3.5 database (Access 97) into a JET 4.0 database (Access 2000 or later)
that you can expect to receive this error if using either Access 2000 or
2002. You will not receive this error if using Access 2003, because all new
databases in Access 2003 include a reference to the DAO library by default.
The same is not true of new databases created with either Access 2000 or 2002.
Finally, it is possible that some action, such as uninstalling a software
app., caused the DAO object library to become unregistered.
Tom
http://www.access.qbuilt.com/html/ex...tributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
"SharonInGeorgia" wrote:
Your explanation on how to resolve this problem is helpful. However, I would
like to know what is happening behind the scenes. Why did my code work fine
in the first database but no longer works in the new copy? What is the
reason for changing the references in the Microsoft DAO 3.51 Object Library?
I've copied many Access Databases in the past but never had the 'dim dbs'
error message before and would like to understand why this error message
appeared.
Similar Threads
