Received: from smtp.screaming.net (smtp.screaming.net [212.49.224.20]) by hub.org (8.10.1/8.11.0) with ESMTP id e9GKMvW98826 for ; Mon, 16 Oct 2000 16:22:57 -0400 (EDT) (envelope-from jamie@sagaxis.co.uk) Received: from mypc.sagaxis.co.uk (dyn201-ras48.screaming.net [212.188.143.201]) by smtp.screaming.net (8.9.3/8.9.3) with ESMTP id UAA03433 for ; Mon, 16 Oct 2000 20:26:10 GMT Message-ID: Date: Mon, 16 Oct 2000 21:16:40 +0100 To: pgsql-interfaces@postgresql.org From: Jamie Walker Subject: Re: Strange Access and PgSQL ODBC References: <01C03744.C1ACB940@CHARLES> In-Reply-To: <01C03744.C1ACB940@CHARLES> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U X-Archive-Number: 200010/127 X-Sequence-Number: 1484 In article <01C03744.C1ACB940@CHARLES>, Charles Killmer 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."