From: =?iso-8859-1?Q?F=E4rber=2C_Franz-Josef_=28StMUK=29?=
	<Franz-Josef.Faerber@stmuk.bayern.de>
To: "pgsql-odbc@lists.postgresql.org" <pgsql-odbc@lists.postgresql.org>
Subject: Row Versioning with MS Access
Thread-Topic: Row Versioning with MS Access
Thread-Index: Ad0ZA8nkudOkrWrlQN2khGZa4cuEvA==
Date: Tue, 21 Jul 2026 11:45:01 +0000
Message-ID: <1dfbd19f75cd4301be1e47d64c7cc482@stmuk.bayern.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/1dfbd19f75cd4301be1e47d64c7cc482%40stmuk.bayern.de>
Precedence: bulk

Dear Mailing List,

I'm trying to get Row Versioning to work with MS Access; but I am unfortuna=
te so far.

Program Versions:
* MS Access 365
* PsqlODBC 17.00.00.06
* Postgres 18.4


What I tried:
* add either RowVersioning=3D1 or A4=3D1 into the connection string
* create a linked table with this connection string in MS Access
* edit some row of this table in MS Access
* In Postgres, having ALTER SYSTEM SET log_statement TO 'all', looking if t=
he corresponding UPDATE statement still has a WHERE clause citing ALL colum=
ns, or by now would use the XMIN column.


My reference was:
* https://odbc.postgresql.org/docs/config.html
* https://odbc.postgresql.org/docs/config-opt.html
* https://odbc.postgresql.org/faq.html#4.3


Additional notes:
* I suppose the FAQ 4.3 Item about a missing operator=3D(xid, int4) is just=
 for veeery old Postgres versions? I tested SELECT '12'::xid =3D 12::int4 a=
nd it worked with my Postgres 18.4 .


Do my proceedings make sense?
* How can I detect psqlODBC Row Versioning working? By moticing an addition=
al column XMIN in the MS Access linked table? Well, this is not the case.
* Does MS Access pick up this feature at all?

Thank You.


Regards,
Franz-Josef F=E4rber