O11Y
New Member
Hi,
I've implemented a DTPicker Control (MSCOMCT2.OCX) into a form and it appears to be functioning correctly except for one thing. When I try to tab out of the control the tab position loops back to the first (in my case "day") field and leads to an inescapable loop where you can no longer tab from the control to the other form components.
I've tried implementing a counter for tab / shift-tab presses (in event KeyDown ) and then manually forcing focus into the next component but the OCX control is oblivious to this counter so when I tab out backwards and tab back in I'm transported to the last field because the OCX tabbing has wrapped around. Also any mouse clicking puts the counter out of sync and leads to furthur ""crazy" behaviour. I tried using return no-apply in the trigger to put me one step closer to predictable behaviour but this did nothing at all, perhaps because the DTPicker uses it's own inbuilt tabbing and is not event driven.
My only other idea was to use the callbackKeyDown event and create 2 empty callback fields at either end of the control. This was meeting with some success except that callbackKeyDown doesn't seem to respond to the tab key.
has anyone had any experience with this control or have any ideas?
Thanks.
Olly
I've implemented a DTPicker Control (MSCOMCT2.OCX) into a form and it appears to be functioning correctly except for one thing. When I try to tab out of the control the tab position loops back to the first (in my case "day") field and leads to an inescapable loop where you can no longer tab from the control to the other form components.
I've tried implementing a counter for tab / shift-tab presses (in event KeyDown ) and then manually forcing focus into the next component but the OCX control is oblivious to this counter so when I tab out backwards and tab back in I'm transported to the last field because the OCX tabbing has wrapped around. Also any mouse clicking puts the counter out of sync and leads to furthur ""crazy" behaviour. I tried using return no-apply in the trigger to put me one step closer to predictable behaviour but this did nothing at all, perhaps because the DTPicker uses it's own inbuilt tabbing and is not event driven.
My only other idea was to use the callbackKeyDown event and create 2 empty callback fields at either end of the control. This was meeting with some success except that callbackKeyDown doesn't seem to respond to the tab key.
has anyone had any experience with this control or have any ideas?
Thanks.
Olly