BeforeUpdate event may refer an incorrect record when the forms are based on the same recordset (823221)
The information in this article applies to:
- Microsoft Office Access 2003
- Microsoft Access 2002
- Microsoft Access 2000
This
article applies only to a Microsoft Access project (.adp).
Moderate: Requires basic macro, coding, and interoperability
skills.
SYMPTOMSIn a Microsoft Access Database Project, two forms may be
based on the same recordset. If you edit a record in one form, and then you try
to save the record by using the BeforeUpdate event procedure, an incorrect record may be referred to in the BeforeUpdate event procedure of the second form. This problem occurs when the
following conditions are true:
- Both the forms use the same recordset to access the data
from the table.
- Immediately after editing the record in the first form, a
different record is selected in the second form.
- You have not committed the changes that were made to the
correct record.
WORKAROUNDTo work around this problem, you can use one of the
following methods:
Note You may avoid the problem by committing the change that you made
to the record. REFERENCES For more information about the
BeforeUpdate event procedure, in the Visual Basic Editor, click
Microsoft Visual Basic Help on the Help menu,
type BeforeUpdate event in the Search
for box in the Assistance pane, and then click Start
searching to view the topic.
Modification Type: | Major | Last Reviewed: | 6/30/2005 |
---|
Keywords: | kbEvent kbForms kbprb KB823221 kbAudDeveloper |
---|
|