--- Ian Harding <ianh@tpchd.org> wrote:
> There is a switch in the ODBC configuration under
> OPTIONS | DATASOURCE | PAGE 2 to use -1 as true. I
> think that will make it work, although I have not
> tried it.
I unchecked "Bools as Char" and checked "True as -1"
in psqlodbc 7.03.01.00. I've transferred the data
from Access and added some dummy entries. Brief visual
scans from both Access and psql indicate that it's
working correctly.
(Woohoo! HIPAA compliance, here we come!)
Thanks much,
Andrew
> >>> Richard Huxton <dev@archonet.com> 07/18/03
> 10:41AM >>>
> On Friday 18 July 2003 18:11, Andrew Gould wrote:
> > > They match up pretty much as you would expect
> > > int4=>long integer etc. One
> > > thing to watch out for is booleans - come
> through as
> > > 0/-1 in Access.
> > >
> > > Richard Huxton
> >
> > I'm dealing with this specific issue for the first
> > time. How do you suggest dealing with the boolean
> > incompatibility issue? I can't seem to make
> > checkboxes work; but I want to keep the pgsql
> boolean
> > datatype. Is there a way to change the value input
> by
> > checkboxes? Or do I have to go with the text input
> of
> > T, F, Y or N?
>
> I could have sworn they did work in Access, but I'm
> not in Windows at the
> moment.
>
> The issue I was talking about is that if you pass
> raw SQL to the database
> you'll want to use "T" whereas in recordsets etc you
> can carry on using "-1"
> etc.
>
> If I get back into Windows before I knock off
> tonight I'll have a quick check.
>
> --
> Richard Huxton
> Archonet Ltd
