maskEdBox auto tab behaves incorrectly

I have a control array made of a maskEdBox. The auto tab behaves as expected for lower case letters in a single value entry field, but as soon as you hold the shift key the tab goes backwards. Is this a Microsoft Bug?
Brandon_CampbellSenior Systems AnalystAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Éric MoreauSenior .Net ConsultantCommented:
goes backward to the previous field? this is the normal behavior. check http://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts
Brandon_CampbellSenior Systems AnalystAuthor Commented:
The masked control has a mask of >A. If the user were to hold the shift key and select "N" while the shift key is depressed then its normal for the autotab to go backwards? If this is the case then I will have to code the caps lock and unlock depending on the field.
Éric MoreauSenior .Net ConsultantCommented:
>>If the user were to hold the shift key and select "N" while the shift key is depressed then its normal for the autotab to go backwards?

yes because a "SendKeys TAB" is sent by the MaskTextBox and the SHIFT is pressed so a backtab is interpreted

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Brandon_CampbellSenior Systems AnalystAuthor Commented:
This is a bad behavior for the control. My customer has a entry field that requires a "+" key to be entered in certain situations. Of course this send ths control back if they use the shift+"+" key. I have included in the lost focus event a setfocus to the next control in this situation but this is not the best work around. I could instruct the users to only use the numberpad "+" which works correctly. I will also key the comments and text fields to turn off caps lock on got focuse and return on lost focus.

Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.