> As a follow up, the syntax below works in Access as well, so maybe it 
wasn't
such a good idea to hardcode the "=TRUE" or "=FALSE" into those SQL
statements...

Cheers
Ken

Actually, in hindsight Access itself wasn't such a good idea, but I take 
your point, and thanks for the reply :-)

We were just hoping that there would be a way of making T-SQL understand 
TRUE/FALSE as keywords within an SQL statement.  Oh well. 

Cheers
Simon