problems on INSERTS via ODBC?

6.5.3 running on RedHat Linux 6.0. Front-end running on MS Access 2000
over ODBC on WinNT

I have recently been experiencing some worrying problems whereby an
"INSERT INTO..." query executed in Access succeeds to all appearances.
Opening the linked table or querying it from Access shows that the
records are present. However, on the server itself these records are
not there, nor are they there if you quit Access and enter it again.

I have debug logs to level 2 off the server, and the psql odbc driver
log. I'm trying to understand them to work out if it was my query
which was somehow causing the problem. I'm not very conscious of where
the responsibility is under ODBC connections to report problems, with
the server, or with the driver.

I think I have solved the problems by dropping all indices, rebuilding
them, and redesigning the problematic queries. (One of the functions
in one had an incorrectly specified parameter - however, Access did
not complain while building the insert, and the final insert looks
correct).

I am worried as to whether this might happen again, and worried that
it could happen at all. I don't know whether the problem is in the
client, the server, or the ODBC driver, but the trouble about this
kind of error is that it is the worst type - records apparently being
inserted correctly, but in fact not being so.

I attach a part of the server log - the inserts seem to be being done
on a one-by-one basis, and the partial log attached contains all
references to one of them. Could someone maybe take a look, and see if
what is recorded in these logs explains the behaviour? It seems
particularly odd, because the final insert appears to have nothing
wrong with it!

Yours,
Moray McConnachie

----------------------------------------------------------------------
----------------
Moray(dot)McConnachie(at)computing-services(dot)oxford(dot)ac(dot)uk