Topic created on: June 7, 2008 16:44 CDT by JohnnyVic .

Some basic info... The main application contains a VBA environment. One toolbar pick in the main app will open a second standalone EXE (call it the picker app).

The picker, on user command, communicates 3 values, a VBA function name (probably just a string value) and two others (integer and string) as a call back to the main EXE. The main EXE stores the two values somewhere and executes that VBA function. When the VBA function runs it accesses the two values through a global activex object and does its thing.

Some other observations that may help... The picker cannot be launched without the main app running but can remain open when the main app closes. If the main app restarts, the picker app can continue to function properly.

Also, If one instance of the main app is started without launching the picker app and then a second instance of the main app is started and the picker app is launched from that instance, the picker app will only communicate to the first instance of the main app.

The main app is probably a Visual Studio 6 C/C++ app. The picker app is most likely a Visual Fortran app. The picker app loads the list of available VBA functions and parameter values from a standalone MDB so the communication between the two apps is very simple: intial launch and then a call to probably one function with 3 parameters (VBA function name (string value), integer value and another string value (variable length - contains alphanumeric comma delimited values).

I want to find out how that call is made back to the main app (what that function is and where it is) and to be able to call that function from within another VBA macro within the main app. In other words, bypass the picker app functionality.

Thanks...