Access 2013 - Error 429 when I reference CurrentProject.Connection

Question

I have a question: Why does my VBA code throw an error 429? First, some context.

I purchased Office 2013 Pro Plus through the Microsoft Home Use Program. I uninstalled Office 2010, and installed Office 2013, and everything was fine. Excel continued to calculate, Access doled out data when asked, Word populated my forms via XML; there was happiness in my little world.

Two days ago, I discovered that I could not access an Access .ACCDB from Excel. This is the offending code:

    Public m_conn As ADODB.Connection

    ...

    ...

    Set m_conn = New ADODB.Connection '' Added in desparation

    '' Run-time error '429': ActiveX component can't create object

    Set m_conn = CurrentProject.Connection

The VBA code had not changed. The .ACCDB had not changed. No references were changed.

I discovered remnants of Office 2010 lingering on my computer, and read online that that could be a problem. I deleted all references to Office not 2013 in files, folders, and the registry.

The VBA still generated error 429.

I ran the Fix-It to wipe Office 2013 from my computer. I also followed the instructions for manually removing Office 2013 from my computer, for both 32-bit and 64-bit Office/Windows; there were traces left over from the Fix-It - go figure.

I then scoured my computer again, just for grins. There were references to Office15 EVERYWHERE in files, folders, and the registry. So much for "completely removing".

I once again scrubbed every trace of Office from my computer, then re-installed Office 2013. Checking Account Information in Access, I see that the 32-bit version of Office is installed.

In "C:\Program Files (x86)\Microsoft Office\Office15" I find InfoPath, but no other Office components (there is no space in "Office15").

In "C:\Program Files\Microsoft Office\Office 15", I find the remaining Office components. (there is a space in "Office 15").

This I pondered: Why are 32-bit executables in the 64-bit folder? Perhaps it is only a contrivance, and has no inherent meaning? Whatever.

Why does the VBA code throw an error 429? And how can this be fixed?

Thanks for listening.

Answer 1

"You get the error because..."

um, yeah, obviously.

"Next..."

Office was installed with ClickToRun, and there is no "Repair" option upon re-install.

"...rebuild the machine..."

Not practical. Perhaps it is the ultimate "solution", but I'd like a different opinion, thanks.

Answer 2

You get the error because after all this work your installation is damaged and some objects cannot be created anymore.

Next I would run an Office Repair.

If that does not help, rebuild the machine. At least that takes a known amount of time, while trying to fix this yourself takes an unknown amount of time.