>We are considering setting up a "console" application from which our users can access various designed-in-house VFP applications. For this to work as intended, the console application would have to run as a completely separate thread, totally distinct from the VFP applications which it calls (so that a running application wouldn't "crash" the console, or vice versa.) Each of the initiated VFP applications would be distinct threads from each other as well. What is the best way to achieve this?
>
>The motivation behind this is that all of our in-house applications could then be installed en masse on each PC we set up. The console application could use the Windows logon userid, etc., to identify which applications would be displayed on the console (not all applications would be apparent to a given user.)
>
>We're not committed to this route yet, we're just considering it, so experienced advice in this regard (pro or con) is welcome.
>
>Thanks,
>Randy W.

With the RUN command, a Visual FoxPro application can run another executable. I do it, with a "loader" program: this one will locate which is the latest version of several executables, and automatically run the latest version. Alternately, depending on the parameters passed, the user can select amongst the versions, and perhaps run an older version. My "loader" will then exit, but you could just as well keep a simlar program open if it fits your needs.