[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.odbcnet

NO_DATA error

Tony

9/27/2002 10:11:00 PM

When reading data from a Sybase SQL Anywhere ODBC driver, we get a NO_DATA
error, then the ODBC.NET provider fails after it attempts to read a blank
char column (meaning I have a char(1) column with a blank value). The column
is NOT NULL.

It appears the driver is sending back a null string "" and the ODBC.NET
provider can't handle this. This same driver works flawlessly from C++.

This appears to be a bug in the ODBC.NET provider.

Anyone have any ideas or work arounds?

Tony
2 Answers

Fredrick Bartlett

9/29/2002 12:09:00 AM

0

Here is the Hot fix...
http://www.microsoft.com/downloads/release.asp?ReleaseID=40560&area=se...
rdinal=1

"Tony" <tonyng2@spacecommand.net> wrote in message
news:uwBkdpmZCHA.568@tkmsftngp12...
> When reading data from a Sybase SQL Anywhere ODBC driver, we get a NO_DATA
> error, then the ODBC.NET provider fails after it attempts to read a blank
> char column (meaning I have a char(1) column with a blank value). The
column
> is NOT NULL.
>
> It appears the driver is sending back a null string "" and the ODBC.NET
> provider can't handle this. This same driver works flawlessly from C++.
>
> This appears to be a bug in the ODBC.NET provider.
>
> Anyone have any ideas or work arounds?
>
> Tony
>
>

Tony

10/2/2002 12:55:00 AM

0

Thanks, that did the trick.

Tony

"Fredrick Bartlett" <rick_bartlett@WeDoNET.net> wrote in message
news:u#01UQ0ZCHA.2420@tkmsftngp09...
> Here is the Hot fix...
>
http://www.microsoft.com/downloads/release.asp?ReleaseID=40560&area=se...
> rdinal=1
>
> "Tony" <tonyng2@spacecommand.net> wrote in message
> news:uwBkdpmZCHA.568@tkmsftngp12...
> > When reading data from a Sybase SQL Anywhere ODBC driver, we get a
NO_DATA
> > error, then the ODBC.NET provider fails after it attempts to read a
blank
> > char column (meaning I have a char(1) column with a blank value). The
> column
> > is NOT NULL.
> >
> > It appears the driver is sending back a null string "" and the ODBC.NET
> > provider can't handle this. This same driver works flawlessly from C++.
> >
> > This appears to be a bug in the ODBC.NET provider.
> >
> > Anyone have any ideas or work arounds?
> >
> > Tony
> >
> >
>
>