> On the other hand, I like the idea of having buttons available that DO NOT > have a tab stop...
The issue of whether the button can receive focus strikes me as unconnected with the issue of whether your EEP code should produce the correct, current value of a variable at any given time. I also got stuck with this issue -- in my case it was a command issued from a group bar (like a speed button, non-focusable, but with no equivalent focus-receiving alternative). The work around is to include focus changing code in the EEP (SKIP TO or PROPERTY . . . SET_FOCUS). Although I do wish that the value of the variable were correctly reported even if focus has not left the field, it's a little harder to know what to do with DB fields. In that case the value is stored in two places -- the field you see on the screen and the underlying column in the row buffer. I'm not sure when the row buffer gets updated, and it would probably make more sense for the value received by the EEP to reflect the current state of the row buffer and not what you see on the screen. -- Larry
