Get VI ref for LV executable set to allow multiple instances

Question

I have inherited some LabVIEW code, which I'm not inclined to change, that will run as an executable with multiple instances set to true on a standard Windows PC. There could be up to four of these executables running in parallel on one machine. I need to interact with these four executables programmatically, and I was hoping to use VI Server to get and put values into the FP controls. However, the visible title of these instances is not necessarily known as they change their names depending on their state, which includes a floating point numeric (for example "My Software n=1.234")
Question: From within LabVIEW (my own executable), how do you get a reference to another LabVIEW executable on the same target when there could be n instances of that executable?
Is it possible to get a list of those VIs that are running as an executable? I tried "Application:All VIs In Memory" property but it returns only the VI that the call is inside, and doesn't see the running executable (I'm not surprised).
I thought about using Windows calls to retrieve all window titles and parse them for this executable, but that might not work as the numeric in the title changes rapidly, so no sooner than I've worked out the title it'll already have changed and will no longer be valid for Open VI Reference. 
I'll continue to try a few other ideas, but would appreciate any input from you smart folk out there 
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Answer 1

Question: From within LabVIEW (my own executable), how do you get a reference to another LabVIEW executable on the same target when there could be n instances of that executable?
 I need to interact with these four executables programmatically.
I'm digging deep here.....  Lets toss out any VI ref or method off the top.  You need to interact with running applications.  To make things just a bit more strange you need to interact with specific instances of the same application while those instances are <poofing> in and out of existance beyond the knowledge of "YourApp.exe"
At least they are on the same target
I cannot think of a elegant way to identify a specific app instance of an exe without the app instance itself supplying some of that info upon launch.  The OS is doing the launching and interaction with the app instances and the LVRTE is merely helping interperate the instructions contained in the executable.
Publishing the RunTime read only property App:Active:App to an element of  a single process shared variable array of "apps.active"  might help.    YourApp can read the array and learn what app instances are active.  But I may be going down a rabbit hole here since that merely filters the problem down to "Finding one of a few instances of a particular app that is currently running"  And it involves modifying the application you inherited.  You said you did not want to modify InheritedApp but, IF you chose to, or it becomes necessary anyway, pass App:Active:App + whatever you need to specify instance out of the app when it is called- ( even if its just a filename YourApp and the InheritedAppInstance can use as a data transfer point)
Time for me to sit back and learn something new today.
EDIT: Just did "What you will want to do is configure each instance of the EXE to have different VI server settings (specifically, the port number or service name) "
Jeff