Multi User Error Message with single user in fomr

[Guest]

I am the only user in a form, using Access 2000. The form has a master and
embedded sub form with detail records. I get an error message saying,"You
and another user are atempting to change data at the same time". what causes
the problem, and how do I fix it?

 

[Allen Browne]

There are lots of issues that can trigger this concurrency problem.

Obviously, opening 2 copies of the database is one cause.

Two copies of the data open at the same time can do it. That might be 2
forms where you are editing, or a form and a query, or a form and a
recordset, or ... Memo fields are particularly susceptible to this kind of
thing, even if you are not editing them in both forms. Failure to close and
dereference recordset variables in code can do it. So can performing any
operation that requires you to move record (such as a find, sort, filter,
requery, move, ...) if you have not explicitly saved the record first.

If none of those valid causes apply, the message can also indicate a
corruption of the database. If you have exhaused the list above, try this
sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
and the code syntax is compilable.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[Guest]

Very Helpful. I had already done a few of your suggestions, but will try the
others and let you know.

 

[betwalk]

Allen-

Would these suggestions apply to the situation I described in the
thread titled "Record changed by another user"? (Posted 1/30/6) I am
going to print your reply to Jeannie in this thread and give them a
try.

Betsy

 

[Allen Browne]

I cannot see taht thread in this group, but yes, that's a general hunting
list for concurrency issues.

 

[betwalk]

Hmmm. Must be why I got no replies. Wonder what I did wrong...
Anyway, thanks, Allen for this response. I'll print out your advice
and give it a try. Some of the procedures you mention are new to me,
but I'll back everything up first, just to be safe.

Have a lovely weekend...