Wow!! This must have been one of those quantum particle-like problems:
as soon as i turned on psqlodbc loggiing to look closely at the problem, it vanished!!!!!
Thanks a LOT for your help.
Fred Parkinson
Association of Bay Area Governments
>>> "Tambet Matiisen" <tambet.matiisen@mail.ee> 02/14/03 08:10AM >>>
You can turn on the psqlodbc logging by yourself. Just open Control Panel ->
Administrative Tools -> Data Sources (ODBC), find your DSN and click
Configure.
Tambet
----- Original Message -----
From: Fred Parkinson
To: t.matiisen@aprote.ee ; pgsql-odbc@postgresql.org
Sent: Thursday, February 13, 2003 11:04 PM
Subject: Re: [ODBC] record locks?
Thanks for responding, clearly i should have been more specific in my
description of the problem.
The linked table is a table, created in postgres with the CREATE TABLE
command.
I am trying to update boolean fields through check boxs in Access datesheet
view, and also through bound controls on forms.
I can insert a record through the Access datasheet view by typing a value
into the key field in the '*' record
(the 'add new record' record)
After that I can successfully update fields only if i do so before i leave
that record.
After that, any other changes I try to make to the data, for example check a
check box to
update a boolean field, i get the "the record has been changed by another
user..." message and changes are dropped.
I can make updates to the table subsequently only if i execute sql commands
with the Access execute function.
Since that form of update works, executing a sql query in access, the system
is correctly locating records by the key field value.
When I ran the odbc driver install i unchecked the 'bool as char' box.
I am actually doing no explicit record locking,
No one else is locking the record because we are testing a new system in a
very small development community (2 developers) and the other person is not
here!
When our postgres/unix administrator returns i will ask him to turn on
psqlodbc logging to see what postgres thinks of attempts to update the
fields through bound Access controls and the Access datasheet view.
Thanks for your help with this matter!
Fred Parkinson
