Using the Tab Key to bypass data requirement on a form

[PaulA]

I am trying to prevent data enteres from using the tab key while in a form to move through controls to go to the next (or new) record. Is there a way of doing this? Using the tab key bypasses some safeguards that I have built in to assure complete data entry.

I do not use the "Required" field in the table due to refreshing that occurs at different times in data entry. I have code that determines whether all required fields are entered (when closing the form or going to a new record other than through the tab key).

Any ideas?

Thanks

 

[IR8USLO]

PaulA,
I would just lock the fields that you do not want altered. You may also want to change the TAB ORDER and put all of the "locked" or "restricted" fields at the end...so that people are less likely to even mess with them! I don't know ifyou can delete items from the TAB ORDER option screen? Hmmm....I guess it is something that you can try, but I doubt it would work.

 

[PaulA]

Thanks for your response--

The problem is that users are going to go to a new or different record and bypassing fields that should have a value entered (even an "Not available" value). They are not altering existing data but not entering where they should. I don't want to use the "required" property on the table due to refreshing on the form.

Any other thoughts?

 

[RichMorrison]

You wrote
<<
I am trying to prevent data enteres from using the tab key while in a form to move through controls to go to the next (or new) record.
>>

What's the problem here ?

Is it
A) you don't want the user tabbing to a new record ?
or
B) you just don't like the Tab key ?

If it's B), I can't help you.
If it's A), set the "Cycle" property of the form to "Current Record".

RichM

 

[PaulA]

Nothing personal against tab keys, but the "cycle" property was just what I was looking for.

Thanks.

 

[David R]

Don't forget

The Mouse Wheel, the PageUp/PageDown, and sometimes even the Up/Down arrow keys can change the record as well.

 

[Pat Hartman]

To make sure that your final edits are executed before a record is saved, you should put them in the BeforeUpdate event of the form. You can't reasonably control how a user moves through the fields of a form (and you really don't want to). So, you can't do anything about skipped fields. The BeforeUpdate event of a form is the last event executed before a record is saved. If you put edits in that event, you can cancel the update to prevent erroneous data from being saved.