Auto Tabbing Does Not Work

[lhooker]

I have a form with text boxes. I want to automatically tab through when a single value is entered. I have 'Auto Tab' set to 'Yes' for the first three (3) text boxes (just for testing) in the form. The table definition for each field is set to 'Single' for 'Field Size', 'General Number' for 'Format', 0 for 'Decimal Places', and 9 for the 'Input Mask'. When entering a value in the first text box, the cursor moves to the second text box, but stop there and the cursor does not move automatically to the next text box. Also, the 'Tab Index' numbers are one (1) digit larger than the previous text box and the 'Tab Stop' is set to 'Yes'. Am I missing something ?:banghead:

 

[Pat Hartman]

Unless EVERY control accepts a fixed number of characters, auto tab is simply confusing because it upsets the rhythm of data entry. If the first three textboxes (this only works with textboxes BTW), have 3, 4, and 2 characters and all characters are always entered but the fourth field is a number defined as single and the fifth is a date, and then you're back to fixed width for a couple of controls, the user's rhythm gets interrupted because he has to remember to tab for the number and date field but if he tabs for the others, he'll skip over them. in order for the single field to autotab, you would need to enter a 5 digit integer and even that might not work because the number could still have some number of decimal places as long as the integer isn't larger than 32K.

All in all, the "feature" has little use. The consistency of having to tab doesn't cause the users to loose focus.

 

[lhooker]

What is the alternative (if any) ?

 

[lhooker]

Is there any other way to automatically tab to the next field after value has been entered ?

 

[Beetle]

You could potentially code for it but you would have to code for every control on your form, counting key strokes until some predetermined number of characters had been entered, plus trying to validate the entry, then code the Tab move. However, I agree with Pat. All of this would likely just end up being a confusing and counter intuitive data entry experience for the user. Things like this sound good in theory but don't usually work well in practice. What if something changes in the future and the given field now needs to accept data of a different character length, etc? You would then need to go back and modify all of your code / input masks / whatever.

 

[Pat Hartman]

Is there any other way to automatically tab to the next field after value has been entered ?

No. Access isn't prescient. Auto tab works only because the field lengths are fixed. If you allow three characters and three characters have been entered, Access knows it can move. If you allow four characters and three are entered, how is Access supposed to know it should move????

Don't try to control the navigation at this level. It is not necessary and there is no way you can do it without confusing the users. Tab is a natural motion. If you prefer, you can make the enter key work like the tab key but I don't like that either since that makes your form work differently from every other form they might encounter. Consistency is critical for accurate data entry. That is the design advice you will get from every book or article ever published. I didn't just make it up.

 

[lhooker]

Pat/Sean,

Thanks ! ! !