[unixODBC-support] Unix ODBC ignores errors posted by SQLBrowseConnect with SQL_NEED_DATA

Nick Gorham nick.gorham at easysoft.com
Thu Oct 18 19:22:32 BST 2007


Chris Seymour @ Simba wrote:

>The spec: http://msdn2.microsoft.com/en-us/library//ms714565.aspx
>
>"SQLBrowseConnect also returns SQL_NEED_DATA if there are recoverable,
>nonfatal errors during the browse process; for example, an invalid
>password or attribute keyword supplied by the application. When
>SQL_NEED_DATA is returned and the browse result connection string is
>unchanged, an error has occurred and the application can call
>SQLGetDiagRec to return the SQLSTATE for browse-time errors. This
>permits the application to correct the attribute and continue the
>browse."
>
>I post a 28000 (authentication failure) error in my driver during
>SQLBrowseConnect() when someone gives bad authentication credentials,
>and return SQL_NEED_DATA so they don't have to start the whole
>SQLBrowseConnect() process over again (as detailed in the quoted part of
>the spec). However, it seems like UnixODBC is completely ignoring the
>error I've posted and isn't returning it to the app.
>
>
>
>  
>
I will take a look then.

Have you looked at the unixODBC code and have you any views about what 
needs changing to make it work for you?

-- 
Nick



More information about the unixODBC-support mailing list