From: | Michael Davis <michael(dot)davis(at)prevuenet(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | RE: [INTERFACES] Yet Another ODBC problem... |
Date: | 1999-02-20 21:24:18 |
Message-ID: | 93C04F1F5173D211A27900105AA8FCFC0281B4@lambic.prevuenet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
I am doing the same thing right now. I found that teaking the data types of
the tables in Postgres helps. For example:
Access data type Postgres data type
Boolean int2
>char(20) varchar
<=char(20) char
The use of varchar over char seem to help the most with errors, especially
with long character fields.
Thanks, Michael
-----Original Message-----
From: J. J. Franzen [SMTP:jj(at)lacasabonita(dot)com]
Sent: Saturday, February 20, 1999 2:15 PM
To: pgsql-interfaces(at)postgreSQL(dot)org
Subject: [INTERFACES] Yet Another ODBC problem...
I've been hunting through the archives of this list for answers to a
specific
problem... I'm trying to link tables from Access 97 to Postgres
6.4.2 and
getting a ODBC call failed error whenever I try to view the table.
Now, I've
found messages discussing the problem, but I can't find any
suggestions on how
to fix, or at least work around, the problem. Any suggestions would
be
greatly
appreciated. Thanks,
J. J. Franzen
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-02-21 11:53:20 | Re: [INTERFACES] ecpg idea |
Previous Message | J. J. Franzen | 1999-02-20 21:15:15 | Yet Another ODBC problem... |