Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to share COM objects between application ?
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Divers
Thread ID:
00855419
Message ID:
00855473
Vues:
13
>Hi Roman,
>
>One way to do it will be to instantiate another COM EXE from your MTDLL and have the apps to communicate through the PUBLIC variable created in the COM EXE. If you instantiate DCOM EXE you will be also able to communicate from different computers through your MTDLL this way. GETOBJECT() is not used there. I demonstrated VFP COM Communicator class and VFP Instant Messenger based on it at my DevCon 2001 session in San Diego.

Nick,
Could you post a simple model of how an EXE COM maintains a puplic variable? Is the COM EXE a VFP COM?

It seems that that instanciation would wipe clean any changes to the public variable? How is the public variable made to persist?

And BTW - your VFP COM communicator class is a marvel. The UT should offer a thread category just so we could pick your brain on that topic:-)

>
>>Hi all,
>>
>>BUG (255683): The GETOBJECT() Function Fails When Calling a Visual FoxPro COM Server
>>
>>How to share the same COM objects between different application running the same computer ?
>>
>>I've created a multi-thread DLL (DEFINE CLASS ComCLT AS Custom OLEPUBLIC), I need to share this DLL between 2 VFP8 application, I'm using :
>>
>>FirstApp, oCom = CREATEOBJECT('clt_com.ComCLT') then
>>in SecondApp oCom = GetOBJECT('','clt_com.ComCLT').
>>
>>In ComCLT :
>>This.Value = ''
>>
>>In FirstAPP :
>>oCom.Value = '1'
>>
>>In SecondAPP :
>>oCom.Value = ''
>>
>>Here's my probem, I can't retrieve the modified value done by FirstApp in the oCom object in SecondApp, how to do ?
>>
>>Best regards,
>>
>>Roman,
>>Microsoft MVP VFP
>>http://www.FoxForum.net
Imagination is more important than knowledge
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform