Re: 2455 error from me.dirty

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Ron Kunce (AID9F5C_at_NoSpam.idpa.state.il.us)
Date: 03/16/05 

Date: Wed, 16 Mar 2005 10:14:10 -0600

I'm sorry this was old problem for which a work-around had been devised and
forgotten about. But now the work-around is causing problems with running a
report from a third called form base on data from the two previous forms
whose changes had not been saved yet and cannot be saved except on the first
calling form. This is an older application in which all the forms are bound
and there was a conflict with trying to save data from a second form to
fields from the same table/record as its calling form. Even if the first
form had no changes, the record still appears to be locked, or at least the
second called form is unable to save changes, nor can it even determine if
itself is dirty (has changes).

The work-around involved writing all the field values from the called form
to hidden fields on the calling form where they would saved when closing the
original calling form. This is proving to be a nightmarish design and I
have concluded it will have to be rewritten with unbound forms or at least
combining the two forms that address the same record into pages on one form,
where there will be no contention.

However, it stills seems strange that the Dirty property of the second form
would throw a 2455 error. Apparently, whatever events are involved it
determining if a form is dirty or not involves having exclusive access to
the record involved.