By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,946 Members | 712 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,946 IT Pros & Developers. It's quick & easy.

Missing DAO 2.5/3.5 Compatibility Library

P: n/a
Hi,
The problem i'm having is that, i've been updating an access 97
database that was originally created in an NT4 environment. My machine
is running xp and the same developers edition of access 97. The current
database runs fine on the users machine with no erros at all. but when
using my updated database all Date() fields appears as Name? and throw
error "missing project or library" when used in code. I also have
problems using Set dbsDatabase As Database commands.

I believe the problem is something to do with the old database using an
old NT4 version of doa2535.tlb and com32dlg.ocx and when i have updated
it, it now uses an xp version of the files which the users access
doesn't recognise.

A quick fix for this would be to access tools --references, and
unclick, reclick the missing files, however this only works for the
time the user is logged in, and reverts back to errors as soon as the
log off/log back on.

I have had the though of downgrading a machine to NT4 and re-working
the whole database in that environment, but that is something i'd
rather avoid as development time is already at 2-3 months.

thanks in advance

Richard

Aug 19 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
This library was to help bridge the gap from early 16-bit versions to Access
95/97. It is now obsolete.

In most databases, it is a relatively easy task to remove it completely, and
just use the DAO 3.6 library. 3.6 recognises most of the old constants. You
can search'n'replace most of the items that won't compile. For example,
find:
Dim MyVariable As Dynaset
and replace with:
Dim MyVariable As DAO.Recordset

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<ka************@hotmail.comwrote in message
news:11********************@b28g2000cwb.googlegrou ps.com...
>
The problem i'm having is that, i've been updating an access 97
database that was originally created in an NT4 environment. My machine
is running xp and the same developers edition of access 97. The current
database runs fine on the users machine with no erros at all. but when
using my updated database all Date() fields appears as Name? and throw
error "missing project or library" when used in code. I also have
problems using Set dbsDatabase As Database commands.

I believe the problem is something to do with the old database using an
old NT4 version of doa2535.tlb and com32dlg.ocx and when i have updated
it, it now uses an xp version of the files which the users access
doesn't recognise.

A quick fix for this would be to access tools --references, and
unclick, reclick the missing files, however this only works for the
time the user is logged in, and reverts back to errors as soon as the
log off/log back on.

I have had the though of downgrading a machine to NT4 and re-working
the whole database in that environment, but that is something i'd
rather avoid as development time is already at 2-3 months.

thanks in advance

Richard

Aug 19 '06 #2

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalidwrote in
news:44*********************@per-qv1-newsreader-01.iinet.net.au:
In most databases, it is a relatively easy task to remove it
completely, and just use the DAO 3.6 library. 3.6 recognises most
of the old constants. You can search'n'replace most of the items
that won't compile. For example, find:
Dim MyVariable As Dynaset
and replace with:
Dim MyVariable As DAO.Recordset
Or just do a COMPILE and Access will tell you everything that needs
to be fixed.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Aug 19 '06 #3

P: n/a
Thanks, worked a treat!

Aug 29 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.