follow up to
not sure if that link is going to work.
Ok, here is the situation:
I have a vbApp called Dps_nbd (if you know what that is, you are in the same building, just come over and talk to me :) ) It is used to hold a dde conversation with a 16-bit app called outside.exe. That part works great.
The problem is, it is not conversing with the correct instance of outside.exe. The dde link needs to be instituted like this:
which works fine, it communicates, but the documentation of outside.exe (outside view) says you can initiate a conversation with a specific instance of ovw if you include the "instance handle"
link.execute "ovw<instance handle>|macro"
--"macro" is required
the problem is, the instance handle is not the handle that is passed from the shell command
'*** begin code ***
new_handle = Shell(outside_path, vbNormalNoFocus)
link.execute "ovw" & new_handle & "|macro"
'alternate link.execute "ovw" & str(new_handle) & "|macro"
'*** end code ***
'*** no communication, it sits and spins forever ***
I have also tried hard coding -link.execute "ovw0|macro" and "ovw1|macro" when I knew only one instance of the program was running, thinking it may enumerate the windows that way, but no soap.
The actual example from the documentation is a dde conversation with excel, as follows:
To use Outside View as a server, connect to OVW (or OVW with the instance handle appended if you are running more than one copy of Outside View). Open the connection with the topic MACRO.
An example of the Excel call noted above is:
OV1 = EXEC("outside.exe async",2)
channel = INITIATE("OVW"&OV1,"MACRO"
so, the questions are:
Does the shell command return the same file handle as enumerating the process using api's would?
Does anyone have a clue what instance handle described above is?
How do I get said instance handle if I have the window caption? (I dictate the window caption, so that is known)
Does anyone have a clue what I am asking?
Am I a fool? (extra points for getting that one right <grin>)