|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 304181 - Last Review: April 11, 2007 - Revision: 6.1 Unexpected write conflict error occurs when you close a form in AccessThis article was previously published under Q304181 Moderate: Requires basic macro, coding, and interoperability
skills.
This article applies to a Microsoft Access database (.mdb) and to a
Microsoft Access project (.adp).
When you edit data that uses multiple forms that have the
same record source, you may receive the following error message:
This record has been changed by another user since you
started editing it. If you save the record, you will overwrite the changes the
other user made.
Copying the changes to the clipboard will let you
look at the values the other user entered, and then paste your changes back in
if you decide to make changes. Then, you can click one of the
following three buttons:
- Save Record
- Copy To Clipboard
- Drop Changes
This behavior occurs when you open two forms that update
the same data source at the same time. The first form puts an edit lock on the
record or records, and then the second form changes the record or records and
saves the changes. When the first form tries to close and write back to the
table, the changes that were made by the second form are detected. This causes
the error to be returned. To work around this behavior, use either of the two methods
listed for a Microsoft Access database (.mdb) file or the method listed for an
Access project (.adp) file. For a Microsoft Access database (.mdb) fileMethod 1 Set the RecordLocks property of the form to Edited Record. To do so, follow these steps:
- Open the form in Design View.
Note In Access 2007, go to step 3. - On the View menu, click Properties.
- On the Data tab, change the Record Locks property to Edited Record.
Method 2 Add code to the OnDeactivate event procedure of both forms to
save the record. To do so, follow these steps:
- Open the form in Design View.
Note In Access 2007, go to step 4. - On the View menu, click Properties.
- On the Edit menu, click Select Form.
- On the Event tab, right-click in the OnDeactivate property box, and then click Build.
- In the Choose Builder box, click Code Builder, and then click OK.
- Type or paste the following code:
DoCmd.RunCommand acCmdSaveRecord
- Open the second form in Design view and repeat steps 2
through 6.
For a Microsoft Access Project (.adp) file: Add code to the OnDeactivate and OnActivate event procedures of
both forms to save the record. To do so, follow these steps:
- Open the form in Design View.
Note In Access 2007, go to step 4. - On the View menu, click Properties.
- On the Edit menu, click Select Form.
- On the Event tab, right-click in the OnDeactivate property box, and then click Build.
- In the Choose Builder box, click Code Builder, and then click OK.
- Type or paste the following code:
DoCmd.RunCommand acCmdSaveRecord
- On the File menu, click Close and return To Microsoft Access.
- On the Event tab, right-click in the OnActivate property box, and then click Build.
- In the Choose Builder box, click Code Builder, and then click OK.
- Type or paste the following code:
Note The sample code in this article uses Microsoft ActiveX Data
Objects. For this code to run correctly, you must reference the Microsoft
ActiveX Data Objects 2.x Library (where 2.x is 2.1 or later). To do so, click
References on the Tools menu in the Visual
Basic Editor, and make sure that the Microsoft ActiveX Data Objects 2.x
Library check box is selected.
Dim rs As ADODB.Recordset
Set rs = Me.Recordset.Clone
rs.Bookmark = Me.Bookmark
DoCmd.RunCommand acCmdRefresh
Me.Bookmark = rs.Bookmark
rs.Close
Set rs = Nothing
- Open the second form in Design view, and then repeat steps
2 through 10.
Steps to reproduce the behavior in Access 2003- Open Access.
- On the Help menu, point to Sample Databases, and then click Northwind Sample Database.
- In the Database window, click Tables under Objects, and then click the Employees table.
- On the Insert menu, click AutoForm.
- Save the form as frmNewEmployees.
- Open the Employees form, and then change the First Name
field to Nancy1.
- Open the frmNewEmployees form, and then change the First
Name field to Nancy2.
- Close the frmNewEmployees form.
- Close the Employees form.
Note that you receive
the "Write Conflict" message that is mentioned in the "Symptoms" section of
this article.
REFERENCES
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
304181Â
(http://kbalertz.com/Feedback.aspx?kbNumber=304181/
)
Unexpected Write Conflict Error When You Close a Form
280730Â
(http://kbalertz.com/Feedback.aspx?kbNumber=280730/
)
ACC2000: Write Conflict Error When You Try to Update Records in a Linked SQL Server Table
APPLIES TO- Microsoft Office Access 2007
- Microsoft Office Access 2003
- Microsoft Access 2002 Standard Edition
| kbado kberrmsg kbprb KB304181 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |