P
Peter Ghali
Infopath has a strange behavior with tabbing when ActiveX controls exist on
the form.
To reproduce the problem, create a form with two controls. The first
control should be an infopath textbox (or other native infopath control). The
second control should be any custom ActiveX control.
Preview the form and you will see that the 'Tab' button moves the cursor
from the first control to the second, just as you would expect. But if you
type something in the first textbox and press 'Tab' the focus gets lost. The
user is required to click the mouse into the control to re-establish focus.
This will be a nuisance during data entry since most people use the tab key
to navigate the form--particularly if the custom control exists within a
repeating section.
Setting the tabIndex property has no effect on the problem.
the form.
To reproduce the problem, create a form with two controls. The first
control should be an infopath textbox (or other native infopath control). The
second control should be any custom ActiveX control.
Preview the form and you will see that the 'Tab' button moves the cursor
from the first control to the second, just as you would expect. But if you
type something in the first textbox and press 'Tab' the focus gets lost. The
user is required to click the mouse into the control to re-establish focus.
This will be a nuisance during data entry since most people use the tab key
to navigate the form--particularly if the custom control exists within a
repeating section.
Setting the tabIndex property has no effect on the problem.