ActiveX Objects

[Guest]

I have a database in Access 2000 (using DAO & OS is Windows 2000) that has
been working fine for several months. The last time I used it was Dec 29,
2005. I just opened it this morning (jan 22, 2006) and am having major
problems. When I try to open certain forms or reports, I get a run time
error -:
Run Time Error '429' ActiveX component can't create object.
If I select debug, the debugger highlights VBA instructions for recordsets.
Some examples are:
set recClone = Me.RecordsetClone
set db = Currentdb
If Me.RecordsetClone.RecordCount = 0 Then

Something seems to have happened to the Office installation since If I
copy the database to another computer, all is fine.
Between Dec 29th and today I have installed the following software:
PowerDVD
Adobe Reader 7
Nero 6
ADS DVD Express (analog video/audio capture device - USB) drivers
and software

Also, I have updated the firmware on my DVD burner. It appears that
somehow one of the Access or Office components was 'corrupted' by one of
these updates.
Any ideas? Or should I try Uninstalling & reinstalling Office 2000 & the
updates?

Thanks -- Garry Gross

 

[Douglas J. Steele]

See whether reregistering DAO360.dll using regsvr32.exe helps.

 

[Guest]

I tend to jump to extreme and unnecessary solutions... but if it's working
fine on other machines, why not re-install office? If that doesn't work, try
creating a new user on the machine and running the app from there.

Nick

 

[Guest]

Now I'm really worried. I tried your suggestion and got the message:
"Load Library "DAO360.dll' failed. The specified module could not be
found!"

However, the file DAO360.dll does exist in :
C:\Program Files\Common Files\Microsoft Shared\DAO

I wonder if the registery is messed up?
Garry Gross

 

[Guest]

I think I've got it working now. In the VBE environment under references,
I unselected DAO 3.6. Then reopened Access and tried to reselect it and it
did not appear in the window!.
I then tried the browse function & selected the actual dll file, it
appeared "checked" and all seems to be working fine.
I have absolutely no idea what could have happened.

Thanks for the lead -- Garry Gross

 

[Guest]

Hi Garry,

You got the Load Library error because you used a path that includes spaces
without using quotes around the entire path. For example, the statement shown
in this KB article is wrong, and will produce the same Load Library error on
any Windows PC:

http://support.microsoft.com/?id=833220 See Method 1, section 2, which
includes the following:

Regsvr32.exe C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll

To fix this, you need to either use double quotes, like this:

Regsvr32.exe "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"

or, use the short path form, like this:

Regsvr32.exe C:\progra~1\common~1\micros~1\dao\dao360.dll


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Now I'm really worried. I tried your suggestion and got the message:
"Load Library "DAO360.dll' failed. The specified module could not be
found!"

However, the file DAO360.dll does exist in :
C:\Program Files\Common Files\Microsoft Shared\DAO

I wonder if the registery is messed up?
Garry Gross

 

[Douglas J Steele]

Sorry, Tom, but I have to disagree with you. The error message wouldn't have
been "Load Library 'DAO360.dll' failed" if that were the case: regsvr32.exe
wouldn't have realized that DAO360.dll was involved, as it would have
stopped looking after C:\Program. (You would have got "Load Library
'C:\Program' failed")

 

[Guest]

Hi Doug,

You're absolutely right. I keyed in on the Load Library error, which I've
received myself when using the directions currently shown in the KB article,
without paying attention to the difference in the results: 'C:\Program
failed' versus 'DAO360.dll failed'.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Sorry, Tom, but I have to disagree with you. The error message wouldn't have
been "Load Library 'DAO360.dll' failed" if that were the case: regsvr32.exe
wouldn't have realized that DAO360.dll was involved, as it would have
stopped looking after C:\Program. (You would have got "Load Library
'C:\Program' failed")

 

[Guest]

I had the same issue where the 429 error message appeared when I loaded a
program. I followed instructions for loading DAO360 but that did not seem to
be the issue as it was sitting where it was supposed to be.

I copied in the command as: regsvr32 "C:\Program Files\Common
Files\MicrosoftShared\DAO\dao360.dll"\dao\dao360.dll" with and without
quotes.
Neither worked. And I cut and pasted and also typed in the command.

Then I tried the: Regsvr32.exe C:\progra~1\common~1\micros~1\dao\dao360.dll
and it successfully registered...

And my program works...

Go Figure.

Best to all.

Jeremy

(e-mail address removed)

 

[Douglas J Steele]

The original path you were using was wrong. It should have been

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

and that should have worked. (You were missing a space in Microsoft Shared,
and you had that extra bit at the end)

 

[csdcom]

I have had the same problem after installing Visual Studio 2005 and
tried everything suggested here and elsewhere to no avial . I have now
fixed the problem but it took a while to work it out. try the following

Go to you Windows directory then go to the inf folder look for the
mdac.inf file right click and select install. When prompted for the
file location point it to your servicepacksfiles directory, this will
reinstall mdac components you may be asked for the handler.reg file
this is on your origial windows CD. This worked form me using XP so in
theory it should be the same for 2K

Charlie

 

[Regina-Astrid Soehnel]

I have had the same problem after installing Visual Studio 2005 and
tried everything suggested here and elsewhere to no avial . I have now
fixed the problem but it took a while to work it out. try the following

Go to you Windows directory then go to the inf folder look for the
mdac.inf file right click and select install. When prompted for the
file location point it to your servicepacksfiles directory, this will
reinstall mdac components you may be asked for the handler.reg file
this is on your origial windows CD. This worked form me using XP so in
theory it should be the same for 2K

Charlie