Setting new reference to DAO360.dll

[Mark Hammer]

Despite re-registering DAO360.dll I still get "error 429: ActiveX component
cannot . . ." on one client computer.

My install program installs dao360.dll in their System32 directory.
However, checking the references in my Access XP file, I see that it is
referring to the file located at Program Files\Common Files\Microsoft
Shared\DAO\.

I tried renaming the file at the MS Shared\DAO location, to force Access to
find the one in System32. However, my system automatically recreates a new
copy of dao360.dll in that location.

I deleted the reference to MS dao360, closed and reopened the references
dialog, hoping that I could add it from the System32 location. However, the
only one listed is the same Microsoft Shared location.

Does it make sense for me to try to force that reference to go to the file I
install in their System32 directory?

Advice/ideas appreciated.

Mark Hammer
Lake Oswego, Oregon, US

[Mark Hammer]

Problem solved when I reregistered the dao360.dll in the Program
Files\Common Files\Microsoft Shared\DAO\ directory, rather than the one in
the System32 directory.

So, for anyone else who has this issue, here is the command prompt entry
which solved my problem:

regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.dll"

don't forget the quotes around the path.

Ta-Da,

--Mark Hammer

"Mark Hammer" <Ma...@AccessAdvantage.com> wrote in message
news:OtH8hZcf...@TK2MSFTNGP06.phx.gbl...

[Tony Toews [MVP]]

"Mark Hammer" <Ma...@AccessAdvantage.com> wrote:

>My install program installs dao360.dll in their System32 directory.

Why? MS includes the dao360.dll as part of the operating system,
since Windows 2000, and updates the dao360.dll automatically as part
of any security patches.

I just started up a clean Windows 2000 guest operating system and
dao360.dll is dated 2008-3-27 version 3.60.9512.0

>Does it make sense for me to try to force that reference to go to the file I
>install in their System32 directory?

No it doesn't. You should not be distributing dao360.dll at all.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

[Tony Toews [MVP]]

"Mark Hammer" <Ma...@AccessAdvantage.com> wrote:

>Problem solved when I reregistered the dao360.dll in the Program
>Files\Common Files\Microsoft Shared\DAO\ directory, rather than the one in
>the System32 directory.

Good. But don't distribute the dao360.dll file yourself.