This is a complete red herring
DLLs leech of the Data Area of their parent EXEs
- although they all share the same Code Area, they all have different
Data Areas - if they belong to different EXEs
There is just one curious exception, which seems to be memory mapped
files - I still have not got to the bottom of that.
Passing data between VB Apps (not VB to CPP) is pretty easy, you
simply use an AX EXE
- which _does_ have its own Data Area
- and hence that is 'shared' between anything using the EXE
(providing the instancing of the AX EXE has been correctly set up)
This is probably of little use for Inter-Language and App
communication - but nifty for VB to VB
On Tue, 08 Jul 2003 05:32:14 -0700, John Norman
<re***@throughnewsgrp.com> wrote:
Stephane,
Do you know which api's handle this?
Thanks
John
On Tue, 08 Jul 2003 00:57:08 GMT, "Stephane Richard"
<st**************@verizon.net> wrote:
Through a dll (written in C++), doesn't work because each app has it's
own instances of the variables declared in the dll. Is there a way to
force one instance?
To this....the API would let you search for an existing instance of the
object and use that one instead of creating a new instance