dspent
asked on
Runtime Error 429 Access 2003/Windows 2000
Our HR dept uses a database to track certain info on volunteers and contractors.... There is a form that has a drop-down list on it where they can select the employee and go to that record....
Three users have access to this database on separate machines....
On ONE machine the user is getting this error when she clicks a name in the list:
Runtime Error '429'
ActiveX component can't create object
One of the other users got this error some time ago and I remember fixing it by re-registering the file
DAO350.dll in c:\program files\common files\microsoft shared\DAO
But the same fix is not working here...
When you click debug on this error you get the following:
Private Sub cboFind_AfterUpdate()
' Find the record that matches the control.
Dim rs As Object
------> Set rs = Me.Recordset.Clone <---------
rs.FindFirst "[Emp_id] = " & Str(Me![cboFind], 0))
If Not rs.EOF Then Me.Bookmark = rs.Bookmark
End Sub
the part i noted above with the ----> <----- signs is what is highlighted in yellow.
Any help is appreciated.
Also, I did not create this DB and do not know anything about how it was created etc....
Three users have access to this database on separate machines....
On ONE machine the user is getting this error when she clicks a name in the list:
Runtime Error '429'
ActiveX component can't create object
One of the other users got this error some time ago and I remember fixing it by re-registering the file
DAO350.dll in c:\program files\common files\microsoft shared\DAO
But the same fix is not working here...
When you click debug on this error you get the following:
Private Sub cboFind_AfterUpdate()
' Find the record that matches the control.
Dim rs As Object
------> Set rs = Me.Recordset.Clone <---------
rs.FindFirst "[Emp_id] = " & Str(Me![cboFind], 0))
If Not rs.EOF Then Me.Bookmark = rs.Bookmark
End Sub
the part i noted above with the ----> <----- signs is what is highlighted in yellow.
Any help is appreciated.
Also, I did not create this DB and do not know anything about how it was created etc....
If this happens on a previously working machine, then the most likely culprit is the DAO .dll file, but apparently that won't work for you. Try doing a repair of the Office installation on that machine (which basicallyl re-registers all the correct dll, ocx, etc etc files) and see if that clears it up. In my experience, if the DAO reregister doesn't work then youll end up pulling out less hair with a repair than anything else. If the repair doesn't work you may need to re-install Access or MDAC ...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No problem from me ... glad you got is fixed dspent.