Printable View
Hi,
I have an ActiveX.dll which I have written to basically share data between two clients.
If I build the client .exes and run them on the desktop and run the .dll in the VB environment, everything works fine.
If I then build the .dll and register it, the .exes can no longer see the shared data.
I don't get any automation errors, so I guess the .exes can still access the component.
Any ideas gratefully received.
A dll is loaded in the address space of the application loading it - so each of your applications has it's own copy of the dll so therefore it can't communicate between them.
When you run it in the VB environment it actually runs as an ActiveX exe pretending to be a dll because you can't actually load the VB IDE into the address space of your calling apps - which is why it works in that mode.
Thanks for the reply,
So I need to build an ActiveX.exe version of the component.
Yes?
Yep, that works a treat.
I should have remembered the bit about .dlls running in process.
One other question, if you have the time.
It takes about 13ms for a client to get data from the ActiveX server running on the same PC.
I know its going to vary from machine to machine, this is a slow old 233MHz
Is that about right? Seems a bit slow to me.