Re: A DLL gone bad ?
- From: Martin <martinvalley@xxxxxxxxxxx>
- Date: Sun, 16 Sep 2007 08:55:41 -0700
On Sat, 15 Sep 2007 01:16:31 -0500, "Ralph"
<nt_consulting64@xxxxxxxxx> wrote:
Clean the Registry.
Re-install the MDAC and Jet Packages for your O/S.
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
Doubtful it will help, but it can't hurt to download and run the Component
tester while you are at it.
Did you perhaps run a MS Security Patch recently? It isn't necessary to
remove the patch, but it might be helpful to look it up on microsoft.com and
see if it specifically affects any MDAC or Jet components.
If using WinXP upgrade to SP2.
I checked out the page you referenced and downloaded and used the
Component Checker. It tells me that I have: MDAC 2.8 SP1. In reality,
I have versions 2.1, 2.5, 2.6, 2.7 and 2.8 on this machine.
I think that the programs having the problems are using 2.5 (at least
that's the one checkmarked in the References list when the program is
loaded into the VB editor).
I verified that I already had copies of the various versions of MDAC.
I tried to install version 2.5 but got a message box saying that it
was already installed and it refused to go any further.
I also tried to install the Jet package but that resulted in the same
message and it would not install it agin.
As mentioned at the top of the thread, this computer has all service
packs and updates installed. The last one installed was whatever MS
released last week (I think it had to do with handling daylight saving
time). But, this was also installed on a couple of other computers
that I'm not having any problems on. The computer has had SP2 on it
ever since it came out.
As you suggested, I ran the program in the editor and, at the
SQLCN.Open statement, the error generated is #3706 - Provider cannot
be found. The "source" of the error is: ADODB.Connection
It seems to me that the problem is in the registry. You mentioned
cleaning the registry. Any recommendations as to how to do this?
.
- Follow-Ups:
- Re: A DLL gone bad ?
- From: Robert Morley
- Re: A DLL gone bad ?
- From: Ralph
- Re: A DLL gone bad ?
- References:
- A DLL gone bad ?
- From: Martin
- Re: A DLL gone bad ?
- From: Ralph
- Re: A DLL gone bad ?
- From: Martin
- Re: A DLL gone bad ?
- From: Ralph
- A DLL gone bad ?
- Prev by Date: Re: working with msaccess 2000 file format in visual data manager
- Next by Date: Re: When I tried to open VB6 VS2005 tries to install!!!
- Previous by thread: Re: A DLL gone bad ?
- Next by thread: Re: A DLL gone bad ?
- Index(es):
Relevant Pages
|