>>>>Ok, here's a good one, I just figured out what mystery has been happening to my screens, and now I can't figure out how to stop it.
>>>>
>>>>It seems that when a check box or option button has the focus and you hit the enter key, a piece of code from another screen in the screen set gets executed. So far, always a piece of code that moves the current screen 600 pix off the screen which is how I switch visible screens.
>>>>
>>>>I've only been able to make this happen with my main application that uses a foundation read. It doesn't happen with small test programs.
>>>>
>>>>Any help would be appreciated, I'd hate to tell my users "just don't do that" with the enter key.
>>>
>>>Does the other code involve a push button with the default set (\!) if so it will always trap the enter button.
>>
>>Well, not always. If you're in a text GET or @EDIT, you have to CTRL+ENTER to press the default button in 2.6, not just ENTER.
>>
>>Rich.
>
>Point taken, but with a foundation read I'm sure this is the problem and removing the default character will fix it.

Yes, sorry, I wasn't contradicting your main point. I'd bet big money the problem is a default button, too.

Rich