From: | Jamie Walker <jamie(at)sagaxis(dot)co(dot)uk> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Strange Access and PgSQL ODBC |
Date: | 2000-10-16 20:16:40 |
Message-ID: | s3g+k+AoI265Ewrd@sagaxis.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
In article <01C03744(dot)C1ACB940(at)CHARLES>, Charles Killmer <charlesk(at)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(at)sagaxis(dot)co(dot)uk destroy your filesystems, eat your data and
http://www.sagaxis.co.uk/ start World War III. You have been warned."
From | Date | Subject | |
---|---|---|---|
Next Message | David Huttleston Jr | 2000-10-16 20:20:24 | Re: wrong documentation and others ..... |
Previous Message | Tony Simopoulos | 2000-10-16 19:03:02 | Re: 2 computers 1hd 2 postgres daemons. Is it possible? |