'record changed by another user' - split form error

Question

Designed in Windows XP Office 2007, running on Windows 7 Office 2010

I have a classic split form with records that show tasks to be done - quotes, call backs, etc.  When a new entry is created the time and date is dropped into a field and then a table is searched to see how long is allowed for the delegate to respond to this particular type of task - 2 hours for a quote, 24 hours for a specially sourced product etc.  So far so good.  At various points along the way a 'time lapsed' field is updated that shows the operator how much time has already expired since the enquiry was received.  Three quarters of the way through the allowed time, the lapsed time field turns yellow and finally, at 'time up', it turns red.  All this works fine.

However, all too often, when a record is modified, be it the notes or whatever, on clicking the save button or clicking into the next record, I get the 'this record has already been editted by another user' (or whatever it is) with the option to save, copy to clipboard or cancel.  Clicking save is actually fine but this shouldn't happen!  The other time it happens (sometimes!) is when you click the tick box to say that the job has been completed.  This has an 'on update' event that drops the time and date into the 'completed time' field and updates the time lapsed field one last time.  Conversely, if you fill the finish time in (by clikcing a little button beside the field) the system also ticks the done box.  Then, on clicking save, the dreaded may, or may not, happen.

Clicking Save is meant to do various things such as update all the time lapse fields, check for incomplete data etc, but I have stripped it back to a plain docmd.save ac form... command and the result is the same.

I thought, perhaps that manually editing the 'Done' tick box and then programmically filling in the time and date made the system think that it had been edited from 2 directions but various experiments prove this not to be the case.

I haven't yet, even after some hours of playing around with it, managed to establish any pattern in its behaviour.  Maybe I have a rogue property that I haven't changed or maybe I'm doing something fundementally wrong - please enlighten me!  I don't use split forms very much as I am not particularly fond of them but I have never had such a persistant problem with this error before.

Please can anyone help before I go completely bald!

Thanks and regards

Geoff

Answer 1

Could you please post the code you are using for these various events?  If you do operations on a form by referencing form controls via "Me" (e.g.,  Me.SomeField = SomeValue) and also update that record via DAO (e.g., CurrentDb.Execute "Update MyTable SET SomeField = 'foo' WHERE MyTable.ID = " & Me.ID), then you can expect a write conflict of this nature.