You cannot use a DLL COM (in-process) to act as a link between to process for the following reasons:
The COM is loaded in the current process (EXE) address space. Each application will load it's own COM instead of sharing one instance of it
A VFP DLL COM cannot display any form on screen and your current code does make use of forms
An multi-Use EXE COM (out-of-process or DCOM) could be used. Other possibilities include:
Message queue (MSMQ)
Sockets (VFP is not a good choice for this. You could build a VB or VC COM for that)
Tables that are shared by both applications to distribute messages
Windows messages (again, a VB or VC COM would be better)
HTH
>I've got a standard application which is Win32 EXE.
>Some code is below>DO MENUS\mainmenu.mpr
>
>IF is_logo( inifile )
> DO FORM splash NAME splashref LINKED
>ENDIF
>
>DO FORM main_panel NAME searchref LINKED
>
>WITH _SCREEN
> oToBeHooked = _SCREEN
> _SCREEN.ADDOBJECT('MyObjectHook','MyHook')
>ENDWITH
>
>READ EVENTS>Would it be difficult ( if possible ) to make it COM server for interapplication communication or intermediate COM DLL would a better approach.
>
>Application1_Com_server <===> Application2_Com_server
>Application1_exe <==>Com_server<==> Application2_exe
