Accessing objects in a DLL, To COM or not to COM
Posted on 1998-08-18
I have defined a base class called TBase with several virtual methods. Based on this TBase class I have inherited several child classes implementing the virtual methods differently. Every child is contained in a DLL with a procedural interface to the constructor and destructor.
In the Main app there is a reference, Base: TBase declared and assigned by the currently loaded DLL constructor. So far, so good. The object behaves real nice until I destroy it. Access violation in the DLL and runtime error 216.
Is this a possible way to do it? Or am I just lucky getting it to work at all? I'm in a hurry and would like not having to dig in to COM right now. Or should I?