MySQL Bugs: #6666: Excel doesn't recognize as registered data provider. dllregistr says ...

Bug #6666	Excel doesn't recognize as registered data provider. dllregistr says ...
Submitted:	16 Nov 2004 14:45	Modified:	31 Jul 2007 6:22
Reporter:	Ross Carver	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51.06	OS:	Windows (Windows XP /Pro)
Assigned to:		CPU Architecture:	Any

Description:
Preamble:  Program written in VBA utilizes mySQL database using ADODB and myODBC 3.51.06 distributed and installed successfully on approximately 50 computers and works fine.

So far, 3 computers after installing myODBC 3.51.06 recognize the myodbc3.dll as a provider when setting up a DSN (testing connection returns success), however, programmatic reference to the myODBC driver returns error stating that it is not recognized. 

First I thought it a problem with the .dll file not being registered properly.  So I try dllregistsvr to register manually.  It reports that the insertion point failed....I research this error, it says the .dll file is corrupt.  I remove the dll file from the system32 directory and re-install.  Same thing.  I try re-downloading the installer package...same thing.

I check the registry keys against a computer where myODBC is installed successfully, and they're exactly the same.  I re-install office, no difference.

I've tried everything I can think of, hoping for some enlightenment.

This software supports our entire field sales operation and I need to find a fix or we're going to have to go to MSSQL for their "support".  Please help.

How to repeat:
If I could get it to repeat consistently I might be better off.  The only thing that I can recall is that it may have been installed while mdac was being installed as well.  This is not certain.

Suggested fix:
I wish.

After further searching.  The behavior of this bug is VERY similar to bug #8230.  See for details.

Err...bug number...  see the following page
http://lists.mysql.com/myodbc/8230

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Hi Ross. We are mixing PROVIDER and DRIVER here. MSDASQL is default provider on 32bit windows. MS described the problem in http://support.microsoft.com/kb/306345.