The problems you encounter are not unique to the NM ActiveX control. Many
of the MS ActiveX control wrappers are made for Visual Basic programmers to
give access to a reduced set of functionality originally exposed through a
much more capable set of COM interfaces. This was also the case with the NM
2.11 ActiveX control. To do the real things you had to operate in C++.
I have experienced a couple of cases where the MS designers apparently
never studied how their controls are accessible in MFC. Last time I
experienced a similar thing with the ActiveX scripting host control. When I
used the regular application framework procedures of adding the control to
my project and then including the control from the tool palette, this
resulted in a header where the run method - most crucial to enable the
scripting host - was "not emitted because of an invalid return type or
parameter type".
Of course there were three ways of bypassing the problem (and that is of
course also the case with yours), but in the end I found that it was more
reasonable to study the MS design patterns from Visual Basic. I would not
bother to spend time on trying to use the NM ActiveX control in MFC for the
simple reason that it is not meant to be used by Visual C++ designers.
Greeting ph
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------
