MySQL Bugs: #4303: Filemaker Pro & MyODBC installation conflict

Bug #4303	Filemaker Pro & MyODBC installation conflict
Submitted:	27 Jun 2004 14:52	Modified:	26 Oct 2004 17:27
Reporter:	D B	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	3.51.8	OS:	Windows (Windows XP)
Assigned to:	Peter Harvey	CPU Architecture:	Any

Description:
The MyODBC driver appears to conflict with the ODBC drivers installed by Filemaker Pro (version 5.5 & version 7) (http://www.filemaker.com). If Filemaker Pro is installed with the complete option (which installs odbc support), and then MyODBC is installed the MyODBC driver is not listed in the "Drivers" Tab of the Data Sources (ODBC) administrative tool, and thus you cannot create a new User or System DSN.

However the MyODBC driver *is* installed. If you uninstall Filemaker Pro, the MySQL driver suddenly becomes visible.

If you reinstall Filemaker Pro, after the MyODBC driver is installed, you will continue to be able to see the MySQL. So there is a workaround.

It appears that the problem only occurs if you run the mysql installer while the filemaker odbc drivers are in place.

How to repeat:
1 Ensure MyODBC is not installed.
2 Install Filemaker Pro (select the 'complete option' to install the ODBC drivers)
Install MyODBC

3 Open the Administrative Tools, Open the Data Sources (ODBC) panel, select the "Drivers" Panel, and observe that MySQL is not listed.

4 Uninstall Filemaker Pro
5 repeat #3. This time MySQL is listed.
6 Reinstall Filemaker Pro
7 repeat #3. MySQL is still listed.

Suggested fix:
I just report them.

I downloaded a trial version of Filemaker 7.0 and using the
File->Import Records-> ODBC data Source I was able for
to access MyISAM and InnoDB tables.

Then I suggest you for to enter in contact with the Filemarker
support for. Feel free for to comment this bug report in case
some repeatable test can be done with Connector/ODBC.

Also the test I did with the version 3.51.09.

Thanks you.

Please re-review the bug. 

A critical repeatability issue with the bug involves the order in which they were installed.

If you install myODBC and then install Filemaker there is no problem. The problem only 
occurs if the filemaker install pre-exists the myODBC install.

To reproduce this bug, myODBC cannot be installed first.  You must install myODBC -after- 
filemaker is installed. Then, if you look at the odbc control panel, you will observe that the 
myodbc drivers are not selectable if you try to create a new data source. The bug only 
affects the panel.

I uninstalled before the MyODBC driver for to test and for my luck my
Win2k is a fresh install for to try again the test . Yes I was able to
repeat in that conditions.

The question now is: It is an MyODBC bug installer ?.
A note in our MyODBC Documentation maybe is the only way for
to handle currently this issue .

Thank you for the bug report.

This Bug is not generated by the MySQL Connector/ODBC-Driver, it's an error/bug from the Microsoft Driver Manager.

I know the bug is generated by the application (Filemaker 5.5 or 7), it is possible when the application writes a new DSN to the registry "odbcinst.ini" and finally  key-item is written to the structure 

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers] 
with name tag coding >>>>    @=""  <<<<. If the DriveManager locate this key, then it doesn't diplay all the drivers after this.

Example:
	[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
	"Microsoft ODBC for Oracle"="Installed"
	"FileMaker Oracle8 Driver"="Installed"
	"FileMaker Text Driver (*.*)"="Installed"
	@=""
	"MySQL ODBC 3.51 Driver"="Installed"

I have downloaded the current version of Filemaker Version 6.0 and Version 7.0, and tested with the bug description and i can see the bug is fixed by Version 6 Filemaker.

I just installed the driver on Win XP sp1 with Filemaker Developer 7.0 v1. installed.  The driver loaded, was displayed in the ODBC Data Source Administrator, and functions properly.

Thanks for the Info.