none
64-bit ODBC driver manager returns 64-bit value for SQLGetConnectAttr(SQL_ATTR_ODBC_CURSORS) RRS feed

  • Question

  • Despite the documentation stating that the attribute value is SQLUINTEGER, the 64-bit ODBC driver manager returns a 64-bit SQLULEN value for SQLGetConnectAttr(SQL_ATTR_ODBC_CURSORS). The other connection attributes, returned by the SQL Server ODBC driver (and SQL Anywhere ODBC driver) are SQLUINTEGER as described by the MSDN documentation for SQLGetConnectAttr. I am using XP Professional x64.

    This deviation from the spec can cause incorrect program behavior. Anyone else stumble on this?

    Monday, May 10, 2010 10:15 PM

Answers

  • Hi jbschueler,

    As Ming confirms the issue you point out is a bug in the ODBC API document.  Please direct your issue to the Data Access forum, which is the team Ming represents, and/or file a bug on the Microsoft Connect site, on the SQL Connect forum.  For the Microsoft Connect site you will need to login with your Live account and join the Microsoft Connect site, as prompted.

    Thank you for bringing this issue to our attention.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Thursday, May 13, 2010 2:12 PM

All replies

  • Hello jbschueler,

    Thank you for your question.  I will investigate this issue and respond with my findings.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Monday, May 10, 2010 11:37 PM
  • Hi jbschueler,

    Can you please point me to the exact specification document and build you are referring to?

    The ones I am aware of are:

    http://msdn.microsoft.com/en-us/library/dd304523(PROT.13).aspx

    http://msdn.microsoft.com/en-us/library/ee320917.aspx

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Tuesday, May 11, 2010 6:48 PM
  • I am looking at SQL_ATTR_ODBC_CURSORS description on ...

    http://msdn.microsoft.com/en-us/library/ms713605%28v=VS.85%29.aspx

     

    Wednesday, May 12, 2010 1:18 PM
  • The version of ODBC on my XP Pro x64 system is ...

        odbc32.dll    C:\WINDOWS\system32\odbc32.dll    N/A    N/A    Symbols not loaded.        4    3.526.3959.0 (srv03_sp2_rtm.070216-1710)    17/02/2007 5:35 AM    000007FF63F00000-000007FF63F67000    [3856] odbc7.exe: Native

        odbccp32.dll    C:\WINDOWS\system32\odbccp32.dll    N/A    N/A    Symbols not loaded.        32    3.526.3959.0 (srv03_sp2_rtm.070216-1710)    17/02/2007 5:35 AM    000007FF63E70000-000007FF63E95000    [3856] odbc7.exe: Native   

        odbcint.dll    C:\WINDOWS\system32\odbcint.dll    N/A    N/A    Symbols not loaded.        19    3.526.1830.0 (srv03_sp1_rtm.050324-1447)    24/03/2005 11:54 PM    000007FF63DC0000-000007FF63DD8000    [3856] odbc7.exe: Native   

    Wednesday, May 12, 2010 1:25 PM
  • First, thanks for your feedback.

    The length of that attribute should be SQLLEN, but not SQLINTEGER. The document is wrong and we will update it as soon as possible.

    http://msdn.microsoft.com/en-us/library/ms713605(VS.85).aspx

    Thanks,
    Ming.
    WDAC Team, Microsoft.

     


    Pak-Ming Cheung - MSFT
    Thursday, May 13, 2010 3:06 AM
  • Hi jbschueler,

    As Ming confirms the issue you point out is a bug in the ODBC API document.  Please direct your issue to the Data Access forum, which is the team Ming represents, and/or file a bug on the Microsoft Connect site, on the SQL Connect forum.  For the Microsoft Connect site you will need to login with your Live account and join the Microsoft Connect site, as prompted.

    Thank you for bringing this issue to our attention.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Thursday, May 13, 2010 2:12 PM