I think I also found one useful switch. In the ODBC-driver's setting there is
one "extra" or so field, where 4 possible values can be entered: 0x0, 0x1,
0x2... If I remember right with 0x2 the driver mimics an SQL-Server auto
increment, which Access acknowledges.
However, does anyone knows go
A comment on the MS access/PG problem.
We experienced this problem as well and I isolated the problem to access's
support of timestamp.
PG defaults to timestamp(6), While access only supports timestamp(2).
When access fills the grid from the table, the values are truncated to ts(2).
