General Question On Control Creation
If the control needs to be public--i.e., will be (or potentially will be)
used by several applications, you'll want to develop it as an OCX. Controls
included within an EXE are not public components. If the control will
certainly be used only within the application in question, you could throw
it into that application. Either way I don't think you'll see a performance
difference, because OCX's run in-process.
HTH-Jon
Quote:
> Hello there coders,
> We are developing a large project that uses ActiveX DLL's for the
> business logic and Forms for the seperate visual interface. As we are
> developing the interface we have found that a need for a control that does
> not exist arises.
> Here is the question.
> Do we develop this control into a seperate project and include
that
> project into the above group, OR do we include the AX control directly
into
> the main application? IE goto add new and then control and have it inside
> the main app?
> Is there a difference? What happens to the control if is included
in
> the main app?
> We have developed AX controls for internal use before but they have
all
> been standalone and required by many projects, the thought of integrating
> them into the main app never occured to us until we downloaded a demo app
> with source and it was included in there.
> Your help is much appreciated.
> Anthoni Gardner
> Software Developer.
> Black-Ice Software.
