Actually in my case it works in neither citrix or network app.
The problems are different between the two, but the screens are
still too unstable in both for the setting to be much good.

>>>Our app does alot of work over Citrix, the new BITMAP = OFF setting
>>>was suppose to reduce screen overload. The problem is that with the
>>>setting active, most of the screens only partially appear, and some
>>>are scrambled. These are NT 4.0 w/Metaframe machines (with the latest
>>>service packs).
>>>
>>>Does anyone have any ideas or experience with this new setting? BTW, BITMAP=ON or removing the entry puts the system back to normal.. Perhaps it works in VFP7..
>>
>>I had the same types of problems with an application a while back. It turned out that it was working great for all users that were accessing the app. through the Citrix (Terminal Server) sessions. But on the desktops running the app. as a general network app. it was doing what you are describing. As you tab through the objects on the forms they appear, or you can minimize/restore. I had to take out the setting as the app. needed to be run as a network app. for some of the users. However as I mentioned it did work great for us on the TS session machines.
>
>If the problem is just when "normal" accesed, but it really speed up things under Citrix/Terminal Server, then maybe you could use two different CONFIG.FPW. That would imply that instead of attaching it to the EXE, you leave it outside, and you use the -C switch to set which one it uses.
>
>Setting each shortcut differently could be a hassle, but you can make two different .lnk files and just copy the one you need in each case.
>
>If someone tries this and it works (or not), I'd be glad to know it!
>
>Good luck.