I am using ODBC to link table to AS/400 DB. This technique works very well except for one very annoying anomaly.
When data is maintained/changed, update action takes immediate effect. However, when end-user re-positions to a different data field and tries to begin a change to the data element in same table/same form/same data row, (just a different field), they get the message:
"The data has been changed. Another user edited this record and saved the changes before you attempted to save your changes. Re-edit the record."
No other user is accessing the record!!! MS is tripping over itself in some technical manner. Data row was updated, and should be released or available for next Database action.
So, does anyone out there know how to suppress, or handle this very unfriendly message? Is there a MS property that controls updates, row locks....?
When data is maintained/changed, update action takes immediate effect. However, when end-user re-positions to a different data field and tries to begin a change to the data element in same table/same form/same data row, (just a different field), they get the message:
"The data has been changed. Another user edited this record and saved the changes before you attempted to save your changes. Re-edit the record."
No other user is accessing the record!!! MS is tripping over itself in some technical manner. Data row was updated, and should be released or available for next Database action.
So, does anyone out there know how to suppress, or handle this very unfriendly message? Is there a MS property that controls updates, row locks....?