Good point, John,
I'm not using Commandbutton.Default=.T. anywhere in my app. The reason I want the enter key to move from field to field is that I am replacing an older DOS-based app where this is the standard behavior. Besides, if you create a form with two or more text boxes on it, pressing the Enter key is just like pressing Tab.

- Werner

>Werner ---
>
>What troubles me about your problem is using the Enter key to move between textboxes. Since the Enter key can be trapped by a Commandbutton.Default=.T., it's a Windows standard to use the Tab key to move between fields.
>
>Does the Tab still work?
>
>I know this does not solve the immediate problem but.....
>
>>I have a formset with various forms. My primary form has command buttons, each of which activates another form. Whenever I activate the one and only form with a grid control on it (which has two columns, one for a checkbox, the other for a textbox) and subsequently activate any of my other forms, the textboxes in the other forms suddenly do not repond to the Enter key, i.e. the focus does not advance to the next object on the form.
>>
>>If I never ever activate the form with the grid control on it, everything else works fine.
>>
>>It's as though accessing the grid control changes the default behavior of my textboxes in general.
>>
>>Is this a bug (version 3.0b) or should I be looking at a property for one of my controls ?
>>