FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

On Wed, 19 Sep 2012 10:19:47 +0100
Frediano Ziglio <freddy77 AT gmail.com> wrote:

> > You have found a bug, by definition.  I think there's something
> > funny in your configuration, something you'll easily be able to
> > fix.  The bug is that you shouldn't be able to get the system to
> > produce that message, no matter what you do.  So I am interested in
> > how it happened.
> >
> 
> No, 100 in ODBC is SQL_NO_DATA. From documentation
> SQLExecute/SQLExecDirect should return SQL_NO_DATA if not data are
> returned. It seems that MS ODBC never return this value. I think that
> I changed (not in 0.91!) our driver to return SQL_NO_DATA according to
> MS ODBC. However it's a bug in isql in this case.

Thanks, Freddy.  It's not isql this time.   bsqlodbc doesn't recognize
100 as a valid return code.  That might be because of this in sql.h:

        #if (ODBCVER >= 0x0300)
        #define SQL_NO_DATA              100
        #endif

src/apps/Makefile.am doesn't define ODBCVER for bsqlodbc.  Perhaps it
should?  

I found http://msdn.microsoft.com/en-us/library/windows/desktop/ms715424
(v=vs.85).aspx.  Words fail me.  

--jkl