missing DAO350

[Mark]

We run an instuction data base using access 2002 and the
runtime version is included with our software. The
problem occurs when one of our customers has access 97
installed. Most of the time a force install on the
runtime fixes thier problem, but at times they get an
error of the DAO350.dll is missing. Our current solution
is to email them a dao350.dll and have them copy it into
c:/program files/common files/microsoft shared/dao. This
doesn't work all of the time, especially when their
access resides on a server. Any ideas would be
appreciated.

 

[Allen Browne]

If you are distributing an Access 2002 runtime, you should include
dao360.dll, not dao350.dll.

If they install Access 97 after your runtime, and the installation manages
to mess up dao360.dll, they should be able to reregister the dll by entering
someting like this at Start | Run:

regsvr32 "c:\program files\common files\microsoft shared\dao\dao360.dll"

Conversely, if your software messes up the A97's ability to use their
dao350.dll, they should be able to re-register with regsvr32.exe. The path
you mentioned is the default location, but they could run a search to see
where the file is. I think it's more likely that the registration of the
file is messed up than that the file is deleted.