Erwin Craps - IT Helps
Erwin.Craps at ithelps.be
Tue Feb 10 01:38:37 CST 2004
Noticed that to.
Don't know if there some general option to change that.
It would seem logical that would be posible.
Erwin
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Eric
Barro
Sent: Monday, February 09, 2004 11:48 PM
To: dba-sqlserver at databaseadvisors.com
Subject: RE: [dba-SQLServer]X-Posted: Problem Converting Bit Fields From
SQLServer 7.0 to SQL Server 2000
Yes SQL server uses 1 or 0 for bit fields.
---
Eric Barro
Senior Systems Analyst
Advanced Field Services
(208) 772-7060
http://www.afsweb.com
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Lawhon,
Alan C Contractor/Morgan Research
Sent: Monday, February 09, 2004 2:31 PM
To: 'accessd at databaseadvisors.com'
Cc: dba-sqlserver at databaseadvisors.com
Subject: [dba-SQLServer]X-Posted: Problem Converting Bit Fields From SQL
Server 7.0 to SQL Server 2000
We upgraded our SQL Server 7.0 backend to SQL Server 2000 over the
weekend. The front end runs Access 2000 GUI client applications.
After the conversion, we are experiencing a problem with Access queries
that select data from the [converted] back end SQL Server tables. The
problem involves a hardcoded "-1" (i.e. "True" logic condition criteria)
in the Access queries testing against a "Bit" data type field in the SQL
Server back end.
With the SQL Server 7.0 backend tables, the Access queries were working
just fine. In converting to SQL Server 2000, it appears that previously
populated bit fields populated with the value of "-1" ("True") got
arbitrarily switched to a value of "1" during the conversion. (The "-1"
values in the back end table ["Bit" fields] got changed, NOT the "-1"
criteria value in the front end query
cells!) Further, when the query runs against the [converted] back end
table, the "-1" criteria (from the Access query) is no longer recognized
- the query doesn't return data.
Needless to say, we are no longer getting the expected results (from
execution of the queries) after the conversion from SQL Server 7.0 to
SQL Server 2000. I suspect that Microsoft implemented a change in the
behaviour of "Bit" fields from version 7.0 to SQL Server 2000. While I
search the Knowledge Base and try to track this down, can anybody
confirm whether this is the case?
We have a lot of queries (and VBA code) that test the "-1" value against
fields of data type "Bit", so we don't want to start changing these
hardcoded criteria (from "-1" to just plain "1") until and unless we are
ABSOLUTELY SURE that this is a SQL Server version 7.0 to version 2000
conversion anomaly.
TIA for any info or enlightenment on this problem.
Alan C. Lawhon
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.580 / Virus Database: 367 - Release Date: 2/6/2004
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com