Albert,

It's a VFP (7) thing. The initial release of VFP 7 had a internal bug where _Screen.AlwaysOnTop can get set to .T. implicitly, and the VFP screen is thereafter always on top.

However, I added code to VMP several builds ago, in both VMP 5 and VMP 2002 to periodically explicitly set _Screen.AlwaysOnTop to .F.

Service Pack 1 of VFP 7.0 fixes this VFP anomaly.

Drew