Method 'connection' of object '_CurrentProject' failed

[Guest]

Hello All,

I have an Access 2000 FE that is set up to launch the standard switchboard
(created through the Access Switchboard Manager) on open. It works fine on
all but one of the WinXP machines on my small office network.

When I attempt to open the application on this particular machine, I get the
following error:
"Run-time Error '-2147220999 (800401f9)': Method 'Connection' of object
'_CurrentProject' failed.

This occurs in the 'FillOptions' procedure which is called from the
switchboard's 'OnCurrent' event at the point where it attempts to open the
table of Switchboard Items (linked), and find the first item for the
Switchboard Page. The line where the error occurs is as follows:
Set con = Application.CurrentProject.Connection

Microsoft KB306132 support article says the problem is likely due to a
damaged or corrupted MDAC stack and recommends installing the latest version
of MDAC. When I download and attempt to install MDAC 2.8 SP1 (the latest
version, I think) I get a message saying there is a newer version already on
the machine and then the installation aborts.

Does anyone have an idea of how to correct this issue?

Many thanks.

 

[Guest]

After some further testing, I can see that the problem XP computer is able to
connect to a data source by creating a System DSN in Admin Tools -> Data
Sources (ODBC). If I create a new text document and save it as "Test.udl,"
however, I get a "Provider cannot be found" error message when I try to open
it. So it appears to be Microsoft's Universal Data Link components that are
causing the issue.

I read a KB article that said that MDAC 2.x could be reinstalled but you
have to be sure none of the included .dll's are in use when you run it. The
msvcrt.dll (Microsoft C Runtime Library) is loaded with just about every
running process though, including explorer.exe, and I have no idea how to
disable it and still keep the machine running. It even loads in safe mode.

It appears that the only resolution is to do a repair installation of XP
unless anyone knows of a way to get around the msvcrt.dll module (is it the
result of some Windows debugging option that could be disabled?). Since
there are a lot more questions than answers posted for this issue, I'm
guessing that a re-installation of the OS is generally required.