Field Cannot Be Updated Error

[mccallradar]

Hello: I am running Access 2007 -

I have a form that when opened uses a macro to go to a new record. All property control settings are set to no locks. It is a shared DB. When I open the form and start to enter new data in the first field I get an error message saying "Field Cannot Be Updated." When I hit help to see what this means, it is saying:

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.

If you hit OK after the error message it goes away and lets you enter data. I don't want the user to get the error. However, if you clear the field and leave it blank, SAVE the RECORD and go to another field the DB doesn't allow you enter any data. I get beep on every keystroke and an message in the bottom saying "Cannot enter value to blank field on 'one' side of outerjoin."

I went to every office desktop. NO ONE HAS THE DB OPEN. Also, all of the values of the controls are set to NO LOCKS.

It worked fine yesterday. Now today I get this new error. I have tried to force the DB to setproperty to enable on open for the first field. I still get the error.

Help, this is driving me crazy!
-Jason

 

[MStef]

Check (via Windows Explorer) is there (in directory) a ".lbd" file (1kb, the same name as your ".mdb"), if it exist, Delete them, and try.

 

[mccallradar]

There is no file like that anywhere. Also, it seems to only be a problem if you run the DB in Access 2007. I ran it in 2003 and it works fine. Any thoughts?

 

[Hugheswt]

I had the same problem with a subform. I compared properties with a similar subform but could not see any obvious differences.

Eventually decided to create a new subform starting with a blank one, I copied the record source from the faulty subform (SQL in this case) and then added all the fields one by one.

I renamed the faulty subform then used the original name for my new one.

Problem now sorted.

I know it does not give a reason for the problem but it worked for me