have developed MFC user dll statically linked to mfc.  the dll is a dialog
box which is a container for a mschart ocx object.
although the dll export function which launches the dialog box (DoModal())
works fine without the ocx, when the ocx is included, the dialog box will
not initialize.  there are no error messages.  Debugging reveals that it is
bombing in the createdialogindirect (mfc) function.  for some reason, the
m_nflags variable is set to 256 after the windows createdialogindirect is
called.  This causes the mfc function to return false.

again, NO ERROR or WINDOW is created.  the dll is loaded from a dialog-based
mfc app.  Is there something i have not included in the dll which is
required for the ocx control?

Bill,

Here's what I found I had to do in an experiment with AX controls in
dialogs in a DLL:

extern "C" __declspec(dllexport) BOOL Pascal ExportedFunction()
{
        AFX_MANAGE_STATE(AfxGetStaticModuleState());

        ::OleInitialize(NULL);

        AfxEnableControlContainer();

        CCalDlg dlg;

        dlg.DoModal();

        ::OleUninitialize();

        return true;

Dave
----
My address is altered to discourage junk mail.
Please post responses to the newsgroup thread,
there's no need for follow-up email copies.