Issues with upgrading VBA application from SQL 7.0 to SQL 2000

[UnderGround]

Hi,
We are using Access 2000 as front end and SQL 7 as the backend. Now we
want to upgrade our database to SQL 2000. I have found out one major
issue as yet which is that our queries were using -1 to check if the
value is true. It works for the SQL 7 databases but does not return
any records when querying SQL 2000 databases. So now we have to go
into all of our access databases and change all the queries to use
true instead of -1. Now my question is does anybody have any idea if
there are any other issues like this that i might face.
Thanks in advance.
Faraz

 

[Pieter Wijnen]

The safest is to check for <>0, Not False is the definition for true in most
programming languages

Pieter

 

[UnderGround]

The safest is to check for <>0, Not False is the definition for true in most
programming languages

Pieter






- Show quoted text -

Thanks but do you know any other issues that might occur?

 

[Pieter Wijnen]

Nope, Only used Oracle, SQL Server 2000 & 2005 myself

Pieter

 

[AnandaSim]

Hi,
We are using Access 2000 as front end and SQL 7 as the backend. Now we
want to upgrade our database to SQL 2000. I have found out one major
issue as yet which is that our queries were using -1 to check if the
value is true. It works for the SQL 7 databases but does not return

AFAIK, SQL Server all versions use 1 and 0 for bit field. Access uses
-1 and 0 for boolean field.

And SQL Server has tristate bit field while Access has dual state
boolean field.

Updating of SQL Server tables with Access may have trouble if the SQL
Server table has no primary key.

Other than that, I don't remember any other problems.

Ananda