Problems with DAO 3.6 Library

[Mr. Smith]

Hi.
I have a shared application which works allright, but when I publish it
through Access 2002 my Access 2000 users seems to have some problem with the
DAO 3.6 Library. I have to uncheck DAO 3.6 in Tools->Refereneces and then
recheck it to make the application work on my 2000 users.

Is there any way I can put the dao360.dll file on a shared network resource,
and point the Reference destination in the application to this file, to make
sure that all users use the same DAO 3.6 Library?

Further: Is there any common approache to working with References, since it
varies from machine to machine, which one are aviable etc. (i.e how to
choose Excel 9.0 when Excel 10.0 Library is not aviable.......)

Grateful for any comments

Mr. Smith

 

[Douglas J. Steele]

Access 2000, 2002 and 2003 should all be capable of using the same files for
DAO 3.6. The fact that you're running into problems implies that you haven't
applied the same Jet 4.0 SPs to all machines.

In answer to your first question, though, you don't want to do what you're
suggesting. DAO360.dll needs to be registered, which means that if put it on
a shared network resource, everyone's registry would be point to it in that
location. Your users would be able to use Access with any database if the
network goes down (or for laptop users not connected to the network).

For the second question, the best approach to having different versions of
applications is to use Late Binding, so that you don't need to set any
references. Tony Toews has some information about this at
http://www.granite.ab.ca/access/latebinding.htm