"Squirrel" <wi*****@covad.net> wrote in
news:67***************************@msgid.meganewss ervers.com:
Suggest doing a Cut and then Paste of the textboxes in your form.
Perhaps that will reset the
creation time of the textboxes in top to bottom order.
The z order is set by when you put the control on the form, so if
you bring the control to front (or sent id to back) you are moving
it in the z order.
I also think the basic task being performed is *wrong* in the first
place. If the value is required, then don't allow the record to be
saved until all fields are filed out. That can be done by having the
AfterUpdate event of each of the required controls check all the
required fields and enable the SAVE button when everything is filled
out. This would include informing a user that a required field can't
be Null if they delete the value in a required field.
I just think it's user-hostile to present multiple validation
messages like this, one field after the other. Instead, it's better,
seems to me, to tell the user that all required fields have not been
filed out, tell them which ones are missing, and then dump them back
to the form, rather than hitting them with message box after message
box.
--
David W. Fenton
http://www.bway.net/~dfenton
dfenton at bway dot net
http://www.bway.net/~dfassoc