Re: 2455 error from me.dirty

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Allen Browne (AllenBrowne_at_SeeSig.Invalid)
Date: 03/16/05 

Date: Wed, 16 Mar 2005 10:24:44 +0800

The message suggests that this form is unbound. Does it have a RecordSource
at all?

Normally you get error 2101 if there is some reason why the record cannot be
saved (e.g. required field is blank.)

If that is not the issue, is there anything else that could have a naming
clash, e.g. a field or text box that is named "Dirty"? Of if there was any
such thing at any stage, Name AutoCorrect could be confusing Access. Or
possibly a corruption of the VBA. 

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Ron Kunce" <AID9F5C@NoSpam.idpa.state.il.us> wrote in message
news:eszcVEZKFHA.3340@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I getting a bit rusty and have run into a problem where a standard call on 
> a
> command button's code of
>
> if me.dirty then. . .
>
> produces a 2455 error message stating that I have entered an improper
> reference to the property "dirty".  I have used this call hundreds of 
> times
> on other forms and I am not sure why this one form is producing this 
> error.
> Hopefully the form has not become corrupt.  However, the record used by 
> the
> form is the same record from the same table as the calling form (which is
> not dirty).  Possibly, this is a conflict between the two forms, both 
> using
> the same record.
> if so, is there a quick work-around other than setting some boolean to 
> true
> every time any field value on the second form has changed?
Quantcast