Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Releasing an application
Message
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 7 SP1
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01003603
Message ID:
01007389
Views:
12
I don't know anything about the Main program, I just put the name of the applcation I developed in a table and it does the rest.
I'm quite sure it calls external application with a DO command as I heredit (I hope this word exists :-) but I mean that i have all the variables and settings from the main program) all the variables and settings from the main EXE program.
I also notice that it seems to release all of the references if i do not use class libraries, but I'm just supposing :-)
Thx for the reply , each answer I get makes my ideas a little bit more...clear
Alessio

>Alessio,
>
>To debug your problem, I think you will have to know how your Main Exe is launching your second application. Since you said that you cannot call CLEAR EVENTS or do any shutdown routines, I assume you are doing something like:
>
>DO MyApp2.app
>
>Does your Main Exe also call READ EVENTS and/or DOEVENTS()?
>
>I have written a few application launchers in FoxPro. To get around the problems you are having, I don't launch them this way. I actually use the Windows API function CREATEPROCESS to launch the executables so that they are completely in their own memory space. That way, you can call all of the cleanup commands that you want and the secondary apps will not interfere with the main app. This also protects your main app from errors or other problems that may occur in your second app.
>
>Another option, which is not nearly as robust as these, is to use the RUN command to launch your second app in its own memory space.
>
>Matthew J. Price
Previous
Reply
Map
View

Click here to load this message in the networking platform