I would suggest either changing the protocol from 6.3 to 6.4 in the
PostgreSQL ODBC driver. My other suggestion was to upgrade the PostgreSQL
ODBC driver but it sounds like you have already done that. I believe the
version you are seeing is the version of the ODBC driver and not the
database server. I am assuming you are using PostgreSQL 6.4.2 or better.
Booleans are another issue. Access97 treats boolean values as int2. It
expects a -1 for true and 0 for false. PostgreSQL treats them as a character
('t' for true and 'f' for false). This means that the word TRUE in Access97
is a -1 and not the 't' that PostgreSQL is expecting. You have two choices
the MS way or the PostgreSQL way. I converted all my booleans to int2 in
PostgreSQL. This was not my first choice but I did not have to change all
of the Access97 queries and code that interacted with boolean values.
-----Original Message-----From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]Sent: Friday, April 30, 1999 10:51
AMTo: 'pgsql-interfaces@hub.org'Subject: [INTERFACES] not translating a query properly. . .
here is my psqlodbc log -- it's short. i have two problems (or may
just one). it still shows using version 6.3, but i completely removed
6.3 (in add/remove programs) and reinstalled 6.4. the other problem i am
having is shown in it too -- i am in an access97 query sql view typing "select
subnum from subs union all select vnum from vend;" (which works great from
the psql prompt), but i am getting some kind of syntax error message.
if you take the time to look into the file you'll also see another ongoing
problem i am having with booleans in my queries (where i am trying to show
all records that are 't' or =1 or any other way i try -- i just bombs).
is there any reason why this query wouldn't run properly? i thought
upgrading to the new version might help. . .
jt << File: psqlodbc.log >>