>I'm not the original creator of the thread, so I don't know. But I'm guessing that what's happening is that he has a button set as the default, and that the button is coincidentally the "next object in the tab order" when he sees the behavior he doesn't want.

After I posted this I saw you (Ian) say you know about Default property of buttons, so I hope I didn't insult you. Again, I'm wondering if this behavior is different depending on version of VFP, because it doesn't act this way in VFP 6.0 on my computer (Win NT Workstation if that makes a difference).

>Cetin said that if there's no default button, [Enter] fires the next button in the tab order by default. It doesn't do that on my computer...if there's no default button, [Enter] moves to the next object. It only clicks a button if there's a default button, and the default button is the button it clicks. I just tested this.
>
>Does this behavior vary from VFP 3.0 to 5.0 to 6.0?

Cheers,