MySQL Bugs: #3724: MySQL ODBC 3.51 Driver version number wrong.

Bug #3724	MySQL ODBC 3.51 Driver version number wrong.
Submitted:	12 May 2004 12:51	Modified:	23 Jul 2004 12:38
Reporter:	Drift	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.07	OS:	Windows (Windows)
Assigned to:	Timothy Smith	CPU Architecture:	Any

Description:
After installation og MyODBC-standard-3.51.07-win.exe
myodbc3.dll shows wrong file version 3.51.06
ODBC Data Source Administrator shows also wrong version.

How to repeat:
Install MyODBC-standard-3.51.07-win.exe on windows 2000
See ODBC Data Source Administrator

Start -> Programs -> Administrative Tools -> Data Sources (ODBC) -> Drivers

MySQL ODBC 3.51 Driver   3.51.06.00   MySQL AB   MYODBC3.DLL    08-05-2004

Suggested fix:
correct version number

Are you ran the installer1s 3.51.07 trying to upgrade the 3.51.06 ?

If yes then is an installer bug, not driver bug already
reported in another bug report.

I removed 3.51.06, then installed 3.51.07, and the version number reported by Windows is 3.51.06. (Win2K SP4)

What is the MyODBC file in your machine like showed
below ?:

C:\>dir c:\winnt\system32\myodb*.dll
 O volume na unidade C não tem nome.
 O número de série do volume é 3C2A-26E8

 Pasta de c:\winnt\system32

31/03/2004  01:30           385.024 myodbc3.dll
               1 arquivo(s)        385.024 bytes
               0 pasta(s) 20.203.761.664 bytes disponíveis

Thanks

C:\>dir c:\winnt\system32\myodb*.dll
 Datenträger in Laufwerk C: ist ATHENA
 Datenträgernummer: 3F3F-14F0

 Verzeichnis von c:\winnt\system32

08.05.2004  02:10              380.928 myodbc3.dll
04.03.2003  00:56              700.469 myodbc3d.dll
               2 Datei(en)      1.081.397 Bytes
               0 Verzeichnis(se),  21.067.464.704 Bytes frei

There may be 2 contributing factors here;

1 - old myodbc did not uninstall completely (which means that its files, registry entries and odbcinst.ini info must be manually removed)

2 - new myodbc installer could have been improperly built (with incorrect version)

I didn't find this bug in my search, but it was pointed out to me after I made a new bug report, so I'll include my own report as a comment, perhaps it will be of some use.

Description: I needed the bugfix which was supposed to be in version 3.51.07 (as
per the bug report: http://bugs.mysql.com/bug.php?id=1102), noticed the
installer being available, then installed the new version using the Windows
"Driver Installer (EXE)" installer. However, when I tested to see if the bug was
fixed, it was not. I did a bit of digging, and noticed that the driver file
myodbc3.dll wasn't being updated. I tried the "Driver Installer (MSI)" version
to see if that would help, with no luck. Looking at the issue a bit closer, I
found out that the 3.51.07 version of myodbc3.dll was reporting itself as
version 3.51.06, so when the installer compared versions, the new one wasn't
newer by version, so it wasn't installed. I managed to get around this by
uninstalling the previous 3.51.06 version then using the 3.51.07 installer.

How to repeat:
1. Have MyODBC version 3.51.06 installed on the computer
2. Run the MyODBC 3.51.07 Windows "Driver Installer (EXE)" installer
3. The new version 3.51.07 will not be installed

Suggested fix:
I believe that simply updating the version number in the driver DLL to properly
report 3.51.07 should fix this problem. Perhaps there are similar issues with
other files such as the object library file, but I didn't investigate those.

Also, the installer size has increased from 731 KB for 3.51.06 to 5.96 MB for
3.51.07, which is quite an increase for what is mostly a small bugfix release.
I'm not sure what could be causing this, but it'd be nice if the size issues
could be looked into as well.

Fixed in 3.51.8