The concurrency error can be caused by a genuine concurrency issue, or by a
corruption.
First, address the possibility of a genuine concurrency issue. Examples:
- code in Form_Open, Form_Load, or Form_Current that dirties the record;
- opening a recordset, and not closing it;
- opening two instances of the database on the same computer;
- opening the same database on two different computers (as distinct from
splitting the database and giving each user their own copy of the front
end);
- having the same data open in two forms at once, particularly if dirty or
if there are BLOB fields (memo, hyperlink, ole object).
It can also help to explicitly save the record before doing anything that
requires it to be saved, such as moving record, applying a filter, setting
OrderBy, changing RecordSource, closing the form, and so on.
If none of those kinds of issues apply, then we are looking at a corruption.
A Decompile is the best bet, though a Name AutoCorrect failure could also
the cause.
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, and reference ambiguities are
resolved.
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
HTH
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
"code 3197" <code (e-mail address removed)> asked the subject question
in message
news:
[email protected]..