>I've determined the behavior is specific to the scrollbar container I've >added to this form. >The Original Code for the scrollbar container is from FoxPro Advisor >10-2005. > >Above the keyboard container is the scrollbar container. This container >contains the textboxes the end user will be using. Pressing standard keys >works like I expect them to work. The only key that isn't working well is >the TAB key. It appears to be working correctly, until I tap another key. >The focus moves to the keyboard container, then all the buttons are >disabled, then focus moves to the next control on the form level. > >I've placed a transparent container above the TAB key and call the click of >the TAB key. It appears to have solved my problem.
I might actually have that issue of FoxPro Advisor--I was subscribing to it around that time. But I don't know where to find it now. What you're describing is mighty odd. Perhaps the scrollbar container does some fancy footwork with mouse events that kabolixes up the VFP event chain. I've observed that if you get too complex with that stuff, VFP will sometimes just throw up its hands and shake its head and go, "Hey, man. I dunno what you want me to do!" Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
