Bug #37254 DSN-less connection prompting within application cannot lookup driver entry
Submitted: 6 Jun 2008 20:20 Modified: 8 Sep 2008 13:41
Reporter: Jess Balint Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Jess Balint
Tags: prompting
Triage: D2 (Serious)

[6 Jun 2008 20:20] Jess Balint
Description:
When providing insufficient information on a DSN-less connection through an application such as Excel, the driver should prompt for the remaining information needed to connect. However, this fails with a message such as "Could not find driver 'MySQL ODBC 5.1 Driver' in system information.".

How to repeat:
In Excel:

Data -> Import External Data -> Import Data
New Source -> Other/Advanced -> Microsoft OLE DB Provider for ODBC Drivers
select "Use connection string", enter something such as "Driver={MySQL ODBC 5.1 Driver}"
Click OK, ("Test connection" tries to connect with SQL_DRIVER_NOPROMPT). Error will be displayed.

Suggested fix:
When using a DSN with insufficient information, prompting works fine, as the driver path (not name) is given. We need to make a distinction between the DSN-based and DSN-less connections when looking up the driver entry for prompting.
[10 Jun 2008 5:43] Jess Balint
fix

Attachment: bug37254.diff (application/octet-stream, text), 6.25 KiB.

[17 Jul 2008 9:21] Lawrenty Novitsky
approved
[30 Jul 2008 16:38] Jess Balint
Committed as rev 1133. Will be released in Connector/ODBC 5.1.5.
[7 Aug 2008 0:48] Jess Balint
Additional fix to myodbc-installer committed in rev 1137.
[8 Aug 2008 16:13] Jess Balint
Additional fixes for 64-bit Windows/WoW committed in rev 1139.
[8 Sep 2008 13:41] Tony Bedford
An entry was added to the 5.1.5 changelog:

The connector failed to prompt for additional information required to create a DSN-less connection from an application such as Microsoft Excel.