>>Peter,
>>
>>I'll watch this thread. This is something I've tried to get around back in the 3.0 days. I can't stand the menu showing. I've even created my own menu with just a single quit on it. The stupid fox menu shows, then my menu and finally my form. Can't help you here.
>click event, and a ShowWindow value of 2, AS-TOP-LEVEL-FORM.
>
>>>I build an exe, run it, and before the form appears I get a white window with Visual FoxPro on the title bar and a few menu buttons for one or two seconds.
>
>FWIW I have the exact same problem with my .exe's. The VFP _screen flashes for about half a second before the top-level form shows. Doesn't _bother_ anything, but it sure is annoying! I don't think this has anything to do with the t-l form or the code in it, but I don't know for sure. I wonder if it would make a difference if the form were objectified and then instantiated instead of being DOne (or DO'ed)?
>
>Paul M.

I've tried everything in the book trying to get it not to act this way. I think it is vfp initially executing, then the .fpw hits and finally the main program code. I finally gave up on this annoyance, I believe the .fpw is the first code that executes, even if it is compiled in the .exe file. If you can't get it to act this way by modifying the .fpw file, then I think the game is over. Even putting a sysmenu = off command as the first line in the .fpw file doesn't help. Nor does it help to put a set sysmenu to ??? command as your first line in your main program. Vfp menu still shows up for a half second.

Robert