Solved
Run-Time error '429': ActiveX component can't create object
Posted on 2009-03-30
We had a PC bite the dust last week. So it had to be reformatted. In doing so, we later realized that some applications needed re-installing that did not have proper documentation on procedure.
This machine runs XP pro SP3 Build 2600 and has a macro in an Excel 2002 worksheet. This worksheet formats and returns data from a Access 97 database. When we first re-installed the Access program it said we did not have licensing on the machine. So we looked up the fix and used the hatten.ttf font fix.
When we went to run the macro we got the error:
Run-Time error '429': ActiveX component can't create object
When we debugged the code it pointed to this section:
====================================================
Public DB1 As Database
Public DB2 As Database
Public ObjConn1
Public ObjConn2
Sub ShowDialog()
UserForm1.LabelProgress.Width = 0
UserForm1.Show
End Sub
Sub Main()
Windows("EmployeeFileFormatted_Expanded.xls").Activate
If Sheet1.CMBcos.Value = "8400" Then
Set DB1 = OpenDatabase("X:\ClientPath\8400.mdb")
Set ObjConn1 = CreateObject("ADODB.connection")
ObjConn1.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=X:\ClientPath\8400.mdb"
Set DB2 = OpenDatabase("X:\ClientPath\8400.mdb")
Set ObjConn2 = CreateObject("ADODB.connection")
ObjConn2.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=X:\ClientPath\8400.mdb"
Else
Set DB1 = OpenDatabase("X:\ClientPath\7426.mdb")
Set ObjConn1 = CreateObject("ADODB.connection")
ObjConn1.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=X:\ClientPath\7426.mdb"
Set DB2 = OpenDatabase("X:\ClientPath\7426.mdb")
Set ObjConn2 = CreateObject("ADODB.connection")
ObjConn2.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=X:\ClientPath\7426.mdb"
End If
Call StartEmployeeFiles
End Sub
====================================================
In this section "X:" is a mapped drive on a server.
After trying several attempts at "complete" unistalling we recieve the same error.
The strange part is this worked on the same station with the same code before the crash, and works on a different station in the office.
Are there any suggestions out there?
Any help would be widely appreciated.