Activex component can't create object

[CD Tom]

I have a friend using Access 2003, I sent him a access database that works just fine on my machine, the first time I ran the program on his machine it worked fine. I didn't make any changes to the program, I closed the program and went back and started it again and this time when I opened the program I get the "Activex component can't create object" I open the program in design mode and check the references, there are no missing references. I've checked each reference to the references on my machine that the program works fine on. Everything is there. I tried doing a trace on the open program but the error comes up before it get to where the trace is to start. I'm starting the trace in many different places just to be sure I check the opening of the program but it still never reaches and of the trace points.
I hope this makes sense to someone and they can point me in the correct direction to getting this fixed.

Thanks in advance for any help.

[zmbd]

Make a backup

For now, if you have any opening code, comment or take it out.

The following is an unsupported feature; thus, I make no guarantees and you use it at your own risk!!!!!!!:
Make a shortcut to Access on the offending machine.
Create a new shortcut to Access and add the decompile switch:
so that for an OFFICE2010 install on a Win7(64b) machine you should have something that looks like this:

"C:\Program Files (x86)\Microsoft Office\Office14\MSACCESS.EXE" /decompile

NOTE the double quotes... these are actually there! I forget what the path and everything was for ACC2003... but it will be something like the afore when done.

Now drag a copy of the offending file, with all startup code disabled, ontop of this shortcut.

If all goes well the DB will open without error.
Close
Make another backup of this new decomplied file
Open the decompiled file using the normal method on the offending PC
VBA - Compile
Database tools compact and repair
close
reopen
re-enable your normal opening vba

See what happens. If this continues then there is an issue with the local PC... and it's simply not possible to go thru everything... either the Office install is bad or something in the OS... could be something in the ActiveX component you're using. If you developed the applicaition in ACC2007/2010/2013 even though you may have saved it as a ACC2003 file, there are some strange things that happen with these files and that could be the unknown issue.

BOL.
-z