🚀 go-pugleaf

"Dennis Jones" <djones@nospam.com> wrote in message
news:403f70b1$1@newsgroups.borland.com...

> the problem there is that the third-party application calls the
> Windows API via a scripting language.

If it is using JScript or VBScript as the scripting language, then it has
access to instantiating COM objects, via the CreateObject() function.  For
example:

    Dim MyObj
    set MyObj = CreateObject("MyApp.MyObject")
    MyObj.DoSomething
    set MyObj = Nothing

> But rather than changing the entire mechanism, it would be much
> easier if there were a simple solution to the problem from within the
> context of the existing mechanism.

I do not recommend using shared memory for communications, unless the shared
memory simply contains an HWND handle to the main app's desired window that
other apps can then send messages to to perform operations.  Otherwise, if
you don't want to go COM, then there are several other IPC (Inter-process
communication) mechanisms available, such as TCP, RPC (Remote Procedure
Call), Pipes, etc.


Gambit