<pv*********@gmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...
Well, not quite... The DLL acts as a wrapper class and the method that
invokes the call to the EXE is actually called from an Access VBA
module.
Unless things have drastically changed for the worse, a DLL is, by
definition, an in-process server. Each exe will reference a different
instance of that DLL. Normally, the way to "call" methods in a standard EXE
(vs and Out of process server... which I have no idea if dotNet supports or
not), you reference your DLL from the EXE, call a method/set a
property/whatever in that DLL and, sometime later, the DLL fires an event.
The exe can trap that event. The DLL can pass any information to the exe as
arguments to the event handler.
I'm just 'poking around' here though so..... In VB6, this kind of stuff is
gravy. Especially when dealing with a VBA back-end.
--
Ken Halter - MS-MVP-VB (visiting from VB6 world) -
http://www.vbsight.com
Please keep all discussions in the groups..
In Loving Memory -
http://www.vbsight.com/Remembrance.htm