Received: from mustang.sdc.com.au (mustang.sdc.com.au [203.2.199.1]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBINLK625253 for ; Mon, 18 Dec 2000 18:21:21 -0500 (EST) (envelope-from scldad@mustang.sdc.com.au) Received: from mustang.sdc.com.au (localhost [127.0.0.1]) by mustang.sdc.com.au (8.9.1a/8.9.1) with ESMTP id JAA20291 for ; Tue, 19 Dec 2000 09:51:24 +1030 Message-Id: <200012182321.JAA20291@mustang.sdc.com.au> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: pgsql-interfaces@postgresql.org Subject: re:ODBC handling of bools? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Dec 2000 09:51:24 +1030 From: Stephen Davies X-Archive-Number: 200012/161 X-Sequence-Number: 505 Thanks to those who replied to my earlier posting. The "Bools as Char" option _was_ the immediate fix. What I had forgotten was that I was using Access as "middleware" and that you have to delete and relink the Access table for the driver change to take effect. (The app involved was originally written for Access and then migrated to Postgresql) My queries now work but the problem now, however, is that the bound checkboxes associated with the bools now give "type mismatch" errors (which they didn't before I changed the driver opton) Cheers and thanks, Stephen Davies ======================================================================== Stephen Davies Consulting scldad@sdc.com.au Adelaide, South Australia. Voice: 08-8177 1595 Computing & Network solutions. Fax: 08-8177 0133