Re: SQL2000 v SQL7 (true/false v 0/1)

#1

"Damian Rafferty" <damianrafferty (AT) tiscali (DOT) co.uk> wrote

Quote:

I have upgraded to SQL2000 from SQL7. I have a VB app that uses ADO.
Previously on returned recordsets from SQL, bit data types stored in the
database as 1 or 0 returned as 1 or 0. Now with SQL2000 they are stored in
the table as 1 or 0 but return as true or false. This has caused some coding
issues. How do I get SQL to return 1 or 0 instead of the boolean value?

Try casting the bit value to an integer, cast(fieldname as int), in a
view over the top of your table, then use the view in your ADO Calls
instead of the table directly.

Tony.

#2

Damian Rafferty (damianrafferty (AT) tiscali (DOT) co.uk) writes:

Quote:

I have upgraded to SQL2000 from SQL7. I have a VB app that uses ADO.
Previously on returned recordsets from SQL, bit data types stored in the
database as 1 or 0 returned as 1 or 0. Now with SQL2000 they are stored
in the table as 1 or 0 but return as true or false. This has caused some
coding issues. How do I get SQL to return 1 or 0 instead of the boolean
value?

SQL Server always return 0 or 1. It does not know what true or false is.
There might be a difference in how ADO handles bit columns, though,
but I don't know of any details about this.

--
Erland Sommarskog, SQL Server MVP, sommar (AT) algonet (DOT) se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: SQL2000 v SQL7 (true/false v 0/1)

comp.databases.ms-sqlserver comp.databases.ms-sqlserver

Re: SQL2000 v SQL7 (true/false v 0/1) - 07-29-2003 , 10:34 AM

Re: SQL2000 v SQL7 (true/false v 0/1) - 07-30-2003 , 03:46 PM