AW: Row Versioning with MS Access

Hello again,

for reasons unbeknownst to me, it WORKS if I close and re-open MS Access.
* The xmin column WILL BE a new column in the linked table.
* The UPDATE stmt now has a short WHERE clause, containing an XMIN condition.

Perhaps I should note I create linked tables using VBA code, and there were already existing connections with DIFFERENT connection strings.

Is anybody familiar what's going on here? Some strange MS Access behaviour? Caching issue? Re-using existing ODBC connections with different Connection Parameters? Something else?

Regards,
Franz-Josef Färber

-----Ursprüngliche Nachricht-----
Von: Färber, Franz-Josef (StMUK)
Gesendet: Dienstag, 21. Juli 2026 13:45
An: 'pgsql-odbc(at)lists(dot)postgresql(dot)org' <pgsql-odbc(at)lists(dot)postgresql(dot)org>
Betreff: Row Versioning with MS Access

Dear Mailing List,

I’m trying to get Row Versioning to work with MS Access; but I am unfortunate so far.

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

What I tried:
* add either RowVersioning=1 or A4=1 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 the corresponding UPDATE statement still has a WHERE clause citing ALL columns, 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=(xid, int4) is just for veeery old Postgres versions? I tested SELECT '12'::xid = 12::int4 and it worked with my Postgres 18.4 .

Do my proceedings make sense?
* How can I detect psqlODBC Row Versioning working? By moticing an additional 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ärber