pop up 7768 error & dirty

  • Thread starter Thread starter NetworkTrade
  • Start date Start date
N

NetworkTrade

In Access02 have a main form with a button that opens a popup form....user
can enter into that popup then close...and all this works fine.

Realized that if they do an "oops"...don't really want that popup...and they
just close it...it is entering a record into the table with no data but the
record's key autonumber and a default timestamp value that is needed in one
field...

So I thought adding a me.dirty=true into the OnClose event if the user's
field is null (meaning they put in no data) but it is throwing a 7768 error
saying that "the cursor must be in a field that can be modified"....a bit
cryptic since the cursor is in the first empty field...

How's the right way to close this form without making a record entry?
 
NetworkTrade said:
In Access02 have a main form with a button that opens a popup form....user
can enter into that popup then close...and all this works fine.

Realized that if they do an "oops"...don't really want that popup...and
they
just close it...it is entering a record into the table with no data but
the
record's key autonumber and a default timestamp value that is needed in
one
field...

So I thought adding a me.dirty=true into the OnClose event if the user's
field is null (meaning they put in no data) but it is throwing a 7768
error
saying that "the cursor must be in a field that can be modified"....a bit
cryptic since the cursor is in the first empty field...

How's the right way to close this form without making a record entry?
Click to expand...

Try using Me.Undo instead of Me.Dirty = True
 
tried your suggestion; no error but still making a blank record entry....

still need a fix...
 
Try testing for null fields and using the me.undo in the form's before update
event. This should catch it before the record is written to the table.
 
Back
Top