First off, you know, you're asking for trouble if you insist on using the Enter key to move between fields in a Windows app? Enter means do the default action for this form, if there is one. I suspect that in your navigation buttons, one of them has its Default property set to .T., which means that pressing Enter is the same as clicking that button.

---

>I've got a system that has been upgraded from FPW2.6 to VFP6. The original screen had a Navigation button row on it that we made into a class, and when we made the VFP form, with the class on it, when data is entered in the text boxes and the Enter key is pressed, the cursor goes to the far left of the text box that it is already in rather than go to the next textbox.
>
>If I create a test form without the navigation buttons, the Enter key works as expected but the minute I put the navigation class on the top of the screen, the Enter key acts as described above.
>
>Any suggestions would be appreciated - especially since I want to get this into production next month and the people who use the old system are used to hitting the 'Enter' key.
>
>BTW, the TAB key DOES work as one expects, but they (and I) prefer the Enter key.