Thread: boolean values and MS Access
I have a boolean column in one of my tables in pgsql. What I would like to do is:
SELECT * FROM public_table WHERE public_table.bShowReport=TRUE;
But I get a data mis-match, although this query works fine from pgAdmin3.
I know Access stores bools a little weird so I have tried public_table.bShowReport=-1; and public_table.bShowReport=”TRUE”
I have tried this as a pass-through query, and it works but I want to feed this query into a report and Access limits your ability to use sub-reports if the parent report is based upon a pass-through query.
I have played around with the “Bools as Char” and “True is -1” settings.
With “Bools as Char” selected I run into problems when Access attempts to edit the field. With “True is -1” I get ODBC Error #7 boolean:=integer
I have tried this with 8.02.04 and 8.02.02. I am hoping there is just some little bit that I am missing.
---
David Gardner, IT
The Yucaipa Companies
(310) 228-2855
Please dis-regard my email. I found someone with a similar problem and the solution in the mailing list archives.
http://archives.postgresql.org/pgsql-general/2006-12/msg00415.php
Apologies for not doing this before I posted.
---
David Gardner, IT
The Yucaipa Companies
(310) 228-2855
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of David Gardner
Sent: Thursday, May 24, 2007 4:08 PM
To: 'pgsql-odbc@postgresql.org'
Subject: [ODBC] boolean values and MS Access
I have a boolean column in one of my tables in pgsql. What I would like to do is:
SELECT * FROM public_table WHERE public_table.bShowReport=TRUE;
But I get a data mis-match, although this query works fine from pgAdmin3.
I know Access stores bools a little weird so I have tried public_table.bShowReport=-1; and public_table.bShowReport=”TRUE”
I have tried this as a pass-through query, and it works but I want to feed this query into a report and Access limits your ability to use sub-reports if the parent report is based upon a pass-through query.
I have played around with the “Bools as Char” and “True is -1” settings.
With “Bools as Char” selected I run into problems when Access attempts to edit the field. With “True is -1” I get ODBC Error #7 boolean:=integer
I have tried this with 8.02.04 and 8.02.02. I am hoping there is just some little bit that I am missing.
---
David Gardner, IT
The Yucaipa Companies
(310) 228-2855
--- David Gardner <David.Gardner@yucaipaco.com> wrote: > Please dis-regard my email. I found someone with a similar problem and the solution in the > mailing list archives. > http://archives.postgresql.org/pgsql-general/2006-12/msg00415.php > > Apologies for not doing this before I posted. this is what I found that worked for me: http://archives.postgresql.org/pgsql-odbc/2006-09/msg00103.php however, MS-Access didn't recognized to boolean fields as yes/no field, so when I used a form creation wizard to start a form, it would used text boxes instead of check boxes. I had to manually replace these controls myself.
I use this function and operator : http://archives.postgresql.org/pgsql-general/2001-10/msg00953.php it just perfectly works with these odbc params : True is -1 -> checked Bools as Char -> not checked -- Guillaume `ioguix` de Rorthais Richard Broersma Jr wrote: > --- David Gardner <David.Gardner@yucaipaco.com> wrote: > >> Please dis-regard my email. I found someone with a similar problem and the solution in the >> mailing list archives. >> http://archives.postgresql.org/pgsql-general/2006-12/msg00415.php >> >> Apologies for not doing this before I posted. > > this is what I found that worked for me: > http://archives.postgresql.org/pgsql-odbc/2006-09/msg00103.php > > however, MS-Access didn't recognized to boolean fields as yes/no field, so when I used a form > creation wizard to start a form, it would used text boxes instead of check boxes. I had to > manually replace these controls myself. > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings