>>>>About the only thing I could suggest here (if SetActiveWindow()) isn't doing it would be to try _SCREEN.Activate in code instead, or SetForegroundWindow().
>>>>
>>>>I've noticed that VFP 7.0 is, for want of a better term, a bit "flakey" when it comes to getting the focus. Every once in awhile, both at home on Win98SE and here at work on Win2K Pro SP2, when I switch from another application to VFP 7.0, I'll start typing and hear a ding. When I look at the screen, nothing's been typed. I then have to click somewhere in the VFP window for it to start getting my input.
>>>
>>>_SCREEN.Activate() nor SetForegroundWindow() does it.
>>
>>Sorry, Michel, but for now, I'm out of ideas. If, however, I find something out or discover something, I'll post back.
>
>I assume that upcoming service packs or release 8 will remove that new "feature" from the product. :)

I really don't know if it will be addressed. I won't be if it isn't known. Perhaps you should ping either Mike Stewart or Jim Saunders.