MySQL Bugs: #37557: Error Message "ODBC driver does not support dynasets"

Bug #37557	Error Message "ODBC driver does not support dynasets"
Submitted:	20 Jun 2008 20:52	Modified:	11 Nov 2009 8:35
Reporter:	Roger Underwood	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	Connector / ODBC	Severity:	S4 (Feature request)
Version:	5.1	OS:	Windows (XP SP3)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	dynaset, keyset-driven

Description:
I am setting up a commercial application by Datacard called ID Works Standard v5.1 to print employee ID badges.  Our goal is to link up the application with our MySQL database instance.  I downloaded the driver "MySQL ODBC 5.1 Driver" and installed it using basic connection parameters (no advanced flags or SSL options configured).  Then I linked up the provider "Microsoft OLE DB Provider for ODBC Drivers" with the driver.  When I run the application it reports the followind ODBC error:  "ODBC driver does not support dynasets".

In researching this on the Web, it looks like everyone is told to recode their applications to not use dynasets.  That seems like fixing the symptom and not the issue, however.  Also, I can't recode the application because it is an off-the-shelf product.

Cam the MySQL ODBC Driver be corrected/enhanced to support dynasets?

How to repeat:
See above.

Suggested fix:
See above.

Hi Roger,

Thanks for bringing our attention to the problem with dynasets.
Due to the fact that dynaset is not an ODBC term and it is mostly applicable to Microsoft libraries such as MFC and DAO I would suggest to use is the following description of what dynasets are:

http://msdn.microsoft.com/en-us/library/ka47a5az(VS.71).aspx

One of the requirements for dynasets availability is support of keyset-driven cursors. Unfortunately, the keyset-driven cursors feature is not supported by both versions of MyODBC driver 3.51 and 5.1.

I will mark this bug report as a feature request, but cannot provide any time estimation for implementing keyset-driven cursors in MyODBC driver. This should be checked with ODBC developers in order to receive more specific info about the problem and when it is going to be solved.

Thanks so much for the prompt response.  Who specifically in the ODBC team can I follow up with to determine a potential availability date?

I have ID Works 5.1 also and have the same problem did anyone find a solution...
hhowell@ci.chula-vista.ca.us

Sorry about that we are connecting to Microsoft visual foxpro driver and the software(Nexwatch) uses the Microsoft OLE DB Provider for ODBC Drivers...

This bug is not scheduled to be fixed at this time.