>>I wonder if anybody has encountered this before.
>>
>>I'm using XP Pro, VFP 7.0.
>>
>>My application gets called as follows:
>>*********************************************
>>do IT.MPR
>>SET CLASSLIB TO basetbr ADDITIVE
>>
>>wait wind nowait "Welcome to " ;
>> + oApp.cNameSystem + ;
>> ", " + ;
>> oApp.cNaUser + ;
>> ". You are attached to the " ;
>> + allt(oApp.cDefDataLoc) + ;
>> " data set. Elapsed time was " + ;
>> allt(str(seco() - oEnv.nTimeBegin,5,3)) + ;
>> " seconds"
>>read events
>>
>>**********************************************
>>
>>Everything works fine when run from within the dev environment. The compiled exe is a different story, however. When I run it, the last thing I see is the WAIT WINDOW NOWAIT in the above code. There is no MDI frame visible, no menu visible.
>>
>>If I go to the task manager, there is an instance of the exe running in the PROCESSES list, but not in the APPLICATIONS list. I'm building it as a Win32 executable. It had previously compiled and run correctly, but now I don't have the foggiest of what happened or where to look.
>>
>>Any suggestions?
>>
>>Andrew
>
>I added _screen.visible = .t. to my environment setup routine and its fixed. I still don't know how it broke!
>
>At one time I had access to the properties window with the _SCREEN object having focus. I can't seem to get this back.
>
>I'm thinking that I inadvertently set the VISIBLE property of the _SCREEN object to .f., and it is stored somewhere, resulting in the unexplained behaviour of my exe.

You can get to the _screen object properties sheet by opening Properties window when there are no visual designers open.