From: Jamie Walker <jamie@sagaxis.co.uk>
To: pgsql-interfaces@postgresql.org
Subject: Re: Strange Access and PgSQL ODBC
Date: Mon, 16 Oct 2000 21:16:40 +0100
Message-ID: <s3g+k+AoI265Ewrd@sagaxis.co.uk> (raw)
In-Reply-To: <01C03744.C1ACB940@CHARLES>
References: <01C03744.C1ACB940@CHARLES>
In article <01C03744.C1ACB940@CHARLES>, Charles Killmer <charlesk@netgai
ntechnology.com> writes
> A while ago I posted a message about stange deletions in a linked table. When
>a value would be entered into the table through access (table or form view), it
>would change all the values on that row to #Deleted, until the table was closed
>and reopend.
Turn ROW VERSIONING on in the advanced properties for the ODBC
connection and re-attach the tables. Make sure that the tables have a
primary key and it should work fine. (NB you will see an extra column
called 'xmin' in each table. You can ignore it.)
HTH,
--
Jamie Walker "While there are no known bugs in it, it might
jamie@sagaxis.co.uk destroy your filesystems, eat your data and
http://www.sagaxis.co.uk/ start World War III. You have been warned."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: jamie@sagaxis.co.uk
Subject: Re: Strange Access and PgSQL ODBC
In-Reply-To: <s3g+k+AoI265Ewrd@sagaxis.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox