Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Catch-22?... or is there a workaround?
Message
From
22/01/2008 14:32:21
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Vista
Miscellaneous
Thread ID:
01284194
Message ID:
01284205
Views:
14
>>I have an odd one here...
>>
>>I have a project with a single top-level form and use both
Application.Visible = .F.
in the Main program and SCREEN=OFF in CONFIG.FPW.
>>
>>However, I cannot successfully re-build the EXE (file access denied) unless I include a
Application.Visible = .T.
in the form's QueryUnload.
>>
>>The result is that the VFP SCREEN shows up after clicking the X-box on the form, needing its X-box (VFP's screen) to be clicked too.
>>
>>Is there a workaround for this... Keep VFP's screen invisible so that it does NOT require to be closed at exit?
>>
>>Thanks
>
>
>Does Windows Task Manager show your .EXE as still running after you exit your application? Sounds like you're not exiting VFP (still in an active READ EVENTS).

Well including Application.Visible = .T. lets the EXE go away properly, so I think the exiting is OK. I also do not get the infamous "Cannot quit VFP" message. But without that line in QueryUnload() it *does* stay in the "Appliations" list of Task Manager.

I tried Borislav's suggestion and I have a similar problem after I run the EXE except that now it appears in Task Manager's "Processes" list! I can run the exe several times and a new item will be added to the "Processes" list for each time. And of course it is not re-buildable in that case too.

Since people achieve this all the time I assume it is doable.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform