Heh.. an icky way is to add columns called "true" (bit, default 1) and "false" (bit, default 0) to every affected table. But I don't recommend that... Daryl At 11:31 AM 2/23/2001 -0600, [EMAIL PROTECTED] wrote: >Hi Everyone, > >Ran into an issue this morning upon upsizing some Access code to SQL Server >7. We had been selecting on Access' yes/no columns like this: > > WHERE active = true > >... which works fine. Upsizing to SQL7, yes/no columns are converted to bit >fields, and the same SQL statement breaks against them. > >The cross-db solution seems to be to modify each query to use: > > WHERE active = 1 > >... since that works in Access and SQL7. But I was just curious if anyone >knows a way to configure SQL7 to allow searching bit columns with true and >false. > >thx, >Ron > > > > > >______________________________________________________________________ >The KCFusion.org list and website is hosted by Humankind Systems, Inc. >List Archives........ http://www.mail-archive.com/cf-list@kcfusion.org >Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED] >To Subscribe.................... mailto:[EMAIL PROTECTED] >To Unsubscribe................ mailto:[EMAIL PROTECTED] > ______________________________________________________________________ The KCFusion.org list and website is hosted by Humankind Systems, Inc. List Archives........ http://www.mail-archive.com/cf-list@kcfusion.org Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED] To Subscribe.................... mailto:[EMAIL PROTECTED] To Unsubscribe................ mailto:[EMAIL PROTECTED]
