>>I didn't say ShellExecute the OCX, wrapper exe.
>
>Aah, sorry, the slow me as usual, but I always appreciated your patience with me.
>
>Now that we have an exe can it be an invisible kind, but got to be fast, can't wait for another VFP session to load. And even then how to communicate parameters to this exe?

Yes it can be visible or invisible. It's fast because it works as if you dbliclicked it separately in explorer. ie:

*Consider it just does this - ignore cpu hog of do while for sample

local ltTime
ltTime=datetime()
do while datetime() < m.ltTime + 3600
enddo

If you ShellExecute 3 instances of it like this:

lnStart = seconds()
ShellExecute(...)
ShellExecute(...)
ShellExecute(...)
? seconds()-m.lnSeconds

Though they all do nothing for an hour your code continues execution immediately.
For passing parameters between them you can use regular parameter passing like command line invocation:

myExe.exe Param1 param2

However between 2 VFP applications you can also use a common table on disk as parameters location. Or an XML file etc.

For example if first one is preparing a cursor and the other one is using it, then I would instead persist it as a table and pass its name. Or pass an xml file keeping info how the 2nd exe could create the cursor itself lifting some more from the shoulders of primary application.
Cetin