Re: CurrentProject.Connection failure


Ok, here's the solution -or, in any case, what worked on my pc- for
this
mysterious bug with CurrentProject.Connection...

Here's the saviour-resource :-)...

http://msauer.mvps.org/images/error.pdf

Steps (1) & (2) are useful for checking MDAC versions and if there are
any
missing files there, but the 'beef' comes with (3) & (4).

For (3), use WinZip to extract the files of the MDAC that corresponds
to
your version of Windows (e.g. MDAC 2.8 SP1) to a temporary folder.

For (4), again use WinZip to extract the files of "mdacxpak" in another

folder.

Then go to folder C:\Windows\inf, find "mdac" (setup information file),

right-click on it and select install as the instructions specify.

During installation, you will probably need to use the Search utility
of
Windows to locate various DLLs (i certainly had to to locate 4-5 DLLs
in
various folders).

In my case the problem was solved once the pc was rebooted.




alex.hatzisavas wrote:
Hi Lyle, and thanks very much.
I tried installing MDAC 2.7 RTM (which is the only one that would get
installed on my machine), but it didn't work.
Also tried using alternative statements (codeproject etc.) but no luck.
So i think i'll just reinstall the product and hope to solve this.

Alex


Lyle Fairfield wrote:
alex.hatzisavas wrote:
Tried this, didn't work.
The problem has to do with a certain functionality of Access being
corrupted.
Would a re-installation help?

I would try running the MDAC component checker found at:

http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en

In the past it has identified for me inconsistencies between the
version of Access and the completeness of the installation of certain
components of MDAC. These inconsistencies resulted in problems with
CurrentProject.Connection; I'm sorry that I cannot remember the details
(I've shut them out of my mind, actually as ITs position was that the
application was flawed, when in fact, their installation of Office or
Windows was flawed; some tension developed at that time, but component
checker supported my position) so I cannot say if they were identical
with yours.

In any case, before resinstalling Access I would try installing the
latest version of MDAC, available from the same site, or its parent.; I
suspect it would be much simpler and just or more likely to cure the
problem.

.

Relevant Pages

  • Re: 429 ActiveX component cant create object when connecting
    ... MDAC is to repair windows with the installation cd. ... Error registering the OCX C:\Program Files\Common Files\System\OLE ...
    (microsoft.public.vb.database.ado)
  • Re: kb832483 problem
    ... Usually this error rises in case if MDAC installation is corrupted. ... you do not have any antivirus running during installation of MDAC. ... For Windows XP you could use Windows XP SP1a (not ...
    (microsoft.public.vb.database.ado)
  • Re: unknown error: 8007007f
    ... get to that folder via the command line, ... > installation of MDAC 2.8 on another computer, ... > the problem server. ...
    (microsoft.public.sqlserver.setup)
  • Re: Packaging Wizard error -2147221163 more info
    ... REMOVE it before reinstalling? ... it deals with a corrupted MDAC installation on the computer. ... > corruption has been reported by several people who use IBM Client Access. ...
    (microsoft.public.access.devtoolkits)
  • Re: cannot open .mpd files in Project 2002
    ... I will try what you say regarding downloading the MDAC. ... as an .mpd and then to try to open it - no go once again. ... Visit www.msproject-systems.com for Project Companion Tools and more ...
    (microsoft.public.project)