Is there a way to set the ODBC driver for SQL server or SQL server to
return this error message when trying to navigate on an empty database
table.

I have one site running Sybase 11 that allways returns this message,
whereas I develop on SQL Server that doesn't. I have tried to find all
the places where the error is triggered, but as I can't duplicate the
error in development it is not very accurate.

TIA

Richard

I think that checking BOF=True AND EOF=True indicates an empty database ?

"richard" <richard+agent@maninfodotcodotuk> wrote in message
news:gdi4qvgje1dosolltsgf10rb285ag0546n@4ax.com...
> Is there a way to set the ODBC driver for SQL server or SQL server to
> return this error message when trying to navigate on an empty database
> table.
>
> I have one site running Sybase 11 that allways returns this message,
> whereas I develop on SQL Server that doesn't. I have tried to find all
> the places where the error is triggered, but as I can't duplicate the
> error in development it is not very accurate.
>
> TIA
>
> Richard
>

On Sun, 2 Nov 2003 11:25:16 +0100, "Werner Huysmans"
<sky38071@skynet.be> wrote:

>I think that checking BOF=True AND EOF=True indicates an empty database ?

That's right, SQL Server and Sybase respond differently when you try
and navigate through an empty table using MS-DAC. Sybase throws an
exception and SQL Server doesn't.

>
>"richard" <richard+agent@maninfodotcodotuk> wrote in message
>news:gdi4qvgje1dosolltsgf10rb285ag0546n@4ax.com.. .
>> Is there a way to set the ODBC driver for SQL server or SQL server to
>> return this error message when trying to navigate on an empty database
>> table.
>>
>> I have one site running Sybase 11 that allways returns this message,
>> whereas I develop on SQL Server that doesn't. I have tried to find all
>> the places where the error is triggered, but as I can't duplicate the
>> error in development it is not very accurate.
>>
>> TIA
>>
>> Richard
>>
>