AllowEdits Bug?

[xPaul]

So, whatever this is whether it is indeed a bug or not I have confirmed exists in Access 2010 on Windows 7 64bit.

In terms of potential work arounds:

Clunky - add an unbound, hidden text box ontop of the existing text box. When the procedure is meant to be ran unhide and bring the value into that new control.

Less clunky - Add control.locked = true after the procedure and add it to the routne for allowedits = true/false to actually allow edits

 

[Galaxiom]

I can see what is going on. The VBA edit leaves the form Dirty allowing further edits. The fix is to save the record after the change.

To use my earlier analogy, once the first driver runs the red light, normally law-abiding drivers can sneak through behind them without the red light camera catching them.

 

[xPaul]

I can see what is going on. The VBA edit leaves the form Dirty allowing further edits. The fix is to save the record after the change.

To use my earlier analogy, once the first driver runs the red light, normally law-abiding drivers can sneak through behind them without the red light camera catching them.

Hi Galaxiom,

What do you recommend in regards to avoiding this?

 

[Galaxiom]

Add this line to your code. (Assuming it is running on the form's module.)

Me.Dirty = False