Re: Can this be done?
- From: "Robert Morley" <rmorley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Nov 2007 16:50:47 -0500
Others have provided the "how to" of it, so let me just provide some "gotchas". I've only played with this sort of setup twice, and it's been a while, but re-entrance is the biggest concern in a shared ActiveX scenario.
For me, the biggest thing to wrap my head around was Public module-level variables. Depending on your design, you may need to share variables between modules, which is nice and easy...but if you want different data for each process that's attaching to your EXE, you'll need to get creative about how you do that.
I was going to go into a bunch of other issues, but it occurred to me that most, if not all, of them are already covered in the VB help file. In the index, look for "Coffee2.vpb sample application". That's got a great primer on attaching multiple applications to a single ActiveX EXE, and some of the issues involved.
Rob
"Kevin Provance" <casey@xxxxxxxxxxx> wrote in message news:eWy%23mTyMIHA.4136@xxxxxxxxxxxxxxxxxxxxxxx
Okay, lets say I have a standard EXE that uses an ActX DLL to store/read and
write program settings. Now, I have a second standard EXE that wants to
access the already created ActX DLL to read settings that are already set.
Obviously I can use my second EXE to create an instance of that DLL, but it
won't have the settings already selected. Is there some trick making the
second program use the instanced DLL without having to create a new one?
Put another way, I want two different programs to share one instance of the
DLL and the settings it holks.
Possible?
.
- References:
- Can this be done?
- From: Kevin Provance
- Can this be done?
- Prev by Date: Re: The inaugural VB6 vs dot net test
- Next by Date: Re: Why the VB6 versus VB.NET contest is baloney
- Previous by thread: Re: Can this be done?
- Next by thread: Why the VB6 versus VB.NET contest is baloney
- Index(es):
Relevant Pages
|
