You have the right list.
I believe this error message is due to access adding "=" signs in the query where postgre doesnt expect them. I think
somebodyhere
posted a fix for this awhile back, I lost the email and would love to have this fix, as i'm sure you would too.
So if the kind gentleman/lady who posted that fix is still paying attention to the list, care to post the fix again?
Thanks in advance
Richard A. Holland
CCNP,MCSE,CCDA
Equitech Information Systems
417.832.0366
----- Original Message -----
From: Frodo Larik <Frodo.Larik@diedenoort.nl>
To: <pgsql-interfaces@postgresql.org>
Cc: <Frodo.Larik@diedenoort.nl>
Sent: Wednesday, December 06, 2000 9:30 AM
Subject: [INTERFACES] PostgreSQL -> ODBC -> MS ACCESS
> Dear Reader,
>
> This is my first post to this list. I just hope this is the right one
> :-)
>
> i'm having a problem with the ODBC connection from PostgreSQL to Access,
> this is what I'm using:
>
> PostgreSQL: 7.02 (Debian/GNU Linux binary)
> MS Access: 97
> ODBC: PostgreSQL ODBC driver on Win32
>
> This is how the table fields looks like this:
>
> =======================
> helpdesk=# \d storingen
> Table "storingen"
> Attribute | Type |
> Modifier
> ------------------+---------+-----------------------------------------------------
> sid | integer | not null default
> nextval('storingen_sid_seq'::text)
> gemeld_by | text | not null
> datum | date | not null
> tijd | time | not null
> ruimte | text | not null
> omschrijving | text | not null
> aktie_door | text |
> response | text |
> afgehandeld | text |
> afgehandeld_door | text |
> Indices: storingen_idx,
> storingen_sid_key
> =======================
>
> This is what is happening:
>
> With Access I enter data into the table via an form, this works all ok
> when only entering new data. When afterwarts I want to change data in a
> already made record OR try to delete the record I get this:
>
> (I see this as a pop-up window in access or on the console of the
> postgresql-server running linux)
>
> ERROR: Unable to identify an operator '=' for types 'xid' and 'int4'
> You will have to retype this query using an explicit cast (#1)
>
> Well I don't know how to fix it, Looked through mailinlists, newsgroups
> etc.., but I can't find a proper solution.
>
>
> I would appreciate If anyone has an solution for this problem, or a
> suggestion ...
>
> Sincerly,
>
> Frodo Larik
>
>
> --
> You plan things that you do not even attempt because of your extreme
> caution.
