Re: A DLL gone bad ?


"Martin" <martinvalley@xxxxxxxxxxx> wrote in message
news:f7kqe31ppgdqucd9ba02um3s1jbsb94opt@xxxxxxxxxx
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.


MDAC packages are labelled with the highest ADO library they support. But
the components for each new version supports interfaces for all previous
versions.

So if you have ADO 2.8 installed, you also have 2.7, 2.6, 2.5, ...
available.


snipped

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?


Just do a google search for "Reg Cleaners" or
http://www.worldstart.com/weekly-download/archives/reg-cleaner4.3.htm
There are quite a few available.

The fact you are asking about Registry Cleaners is scary as you should be
doing this as part of a regular maintenance schedule. Especially on a
Developer Box. XP is perhaps safer than previous Windows, but it's best to
use a little extra help.

As for what exactly is wrong. That is tough - the error message "Provider
not found" means exactly that, and cause can be because of almost anything -
the provider was moved, the registry is corrupted, user doesn't have rights
to folder, etc. All I have suggested so far is just the usual suspects. I
can assure you that the repair will be minor, completely out of proportion
to the trouble it has caused. <g>

In the meantime, look up "Data Link" in the Windows Help (off the Start
Menu). It shows how to create a .udl file to create a connection string and
then test it against a database. Try it.

-ralph


.

Relevant Pages

  • Re: A DLL gone bad ?
    ... Re-install the MDAC and Jet Packages for your O/S. ... but it can't hurt to download and run the Component ... I also tried to install the Jet package but that resulted in the same ...
    (microsoft.public.vb.general.discussion)
  • Re: Runtime Error 3706
    ... > person is running Windows XP SP2. ... So I ran the MDAC Utility Component Checker ... > in the Registry and still no luck. ... There is a situation if you are using DAO and a DAO Control - the DAO360.Dll ...
    (microsoft.public.vb.general.discussion)
  • Re: ODBC(Open Database Connectivity)errors
    ... See if it shows any inconsistencies, and current MDAC version. ... ODBC installation is corrupt, or ODBC has lost the connection to your ... custom does not give MDAC updates and all priority updates are ... I went into Microsoft download centre and had a look at driver downloads, ...
    (microsoft.public.windowsxp.general)
  • Re: VB6 Questions
    ... "Krishna Prabhu" wrote in message ... > I also have confirmed that MDAC is installed successfuly. ... > "Val Mazur" wrote: ... You could download it ...
    (microsoft.public.vb.database.ado)
  • Re: SUS
    ... > the MDAC version, using one of the following methods. ... Then you can remove Q329414, and, we hope, then have SUS work ... > scanning all of the core MDAC files and registry settings. ... > | Updates are not installing from the SUS server. ...
    (microsoft.public.win2000.security)
Quantcast