If I hit F9 then the save works.
If I hit F10 then the current object loses all text that has been entered.
If I do not map F10 to F9 then nothing happens and the text is unchanged.

We use command buttons on all our forms. The keypreview is turned on in the forms and there is a case statement in the form keypress that looks for any hot keys used in the command buttons and if one is hit then a procedure or whatever is run from the case statement. This has worked really well for us for a number of years.

As I said, the Only change that caused this problem is changing the form from Modal to Modeless. If I change the form back to Modal it works ok.
John.


>How F9 is processed?
>
>>For about 20 years we have used the F10 key as the Save Data key in all our programs. When VFP came along the F10 was used by windows as the menu key. We got around that by:

ON KEY LABEL F10 KEYBOARD '{F9}'

and that has worked fine for almost 10 years. Now we have a new problem. I found that if a window is Modeless that hitting the F10 key wipes out any data entered in the current text box, edit box, etc.
>>
>>We set focus to another object before the save so I know that's not it. In fact everything works just fine until I just change a form from Modal to Modeless. This is a big problem for us because there are hundreds of users around the country that will be screaming at us if we change the save key from F10 to say F9 which is the only thing that we can come up with.
>>
>>Can anyone save us from the Angry Hoard?