Error message: Field cannot be updated

[M Skabialka]

I have an Access2000 database which has been running under Access 2007 for
the past year or so and for years before that in 2000 and 2003. Suddenly on
one form which has worked for years there is an error occuring on a subform.
The user tries to add a new record where the first field is a combo, but as
soon as they select something there is a "Field cannot be updated." message.
The help button says:

The field cannot be updated because another user or process has locked the
corresponding record or table. (Error 3164)
Possible causes:
You tried to update a field in a record or table that is currently locked by
another user. Wait for the other user to finish working with the record or
table, and then try the operation again.
In Microsoft Access, you tried to change the value of a control whose Locked
property is set to Yes.

No-one else is in the database. No other forms have that table open. The
locked property has never been set to yes. None of the fields has a default
value.
After clicking OK on the message the field gets populated from the combo and
the record can be created OK and saved after filling in some other required
fields.
Other subforms in the database allow new records with no problem.

What is really causing this message so that I can fix it rather than hiding
it?
Mich

 

[M Skabialka]

The message changed to "You can't assign a value to this object" after I
made copies of each form and subform. Then suddenly it started working. I
had the user try it - the first time there were error messages, but after
closing the form and trying again there aren't any messages. I have
compacted the database several times. Is there something lurking in the
code now for this problem that might surface again later?
Mich

 

[Adr]

I have also got the same error message 3164 after linking the tables to SQL
server. Can you tell me how u corrected it ?

Thanks
Dilip.

 

[M Skabialka]

Apart from compact/repairing, and using the copies I made of the form and
subform, I am clueless as to what really fixed it - so am not sure if it
really is fixed, though the error no longer occurs.