>
> WHERE prov = TRUE.
>
> WHERE NOT prov IS NULL OR prov = FALSE
SQL Server 2000 doesn't understand TRUE or FALSE - it thinks they are a
column reference - booleans are 1 or 0
> This specific case is not a matter of being too used to
> Access' tricks, this is a matter of MS SQL Server not being
> standard compliant. While the code is not exactly an example
> of 'defensive' SQL written with portability in mind, MS SQL
> Server should handle this better. After all, according to
> your classification MS SQL Server is a REAL server level
> database engine, so it is not unreasonable to expect it to
> behave better then his desktop nephew :-)
The same goes for Oracle though, there are certain oddities about Oracle
which are non-standard (like being able to update an Identity column)
which you have to learn to use it properly
Same goes for any of the "big" database engines, there are things which
do and do not work (I don't think mySQL can do sub-queries)
There is no real direct portability apart from the simplest of SQL
statements
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
