Chartfx, first time I know it.

If you disable profiling, does it run as normal? "Approved Workmen Are Not Ashamed" - 2 Timothy 2:15 "Judge not by the eye but by the heart." - Native American Proverb

No the control is handle mouse message just fine but even after clicking in the window several times the key messages don't get through. See my further post regarding how I might have fixed it. My concern now is if I have several of these controls on a dialog which one will respond to the messages. Andrew

My program doesn't really crash. It compiles fine, works fine in the ActiveX Control Test Container but whenever I try place it in another application , be that a Powerpoint slide another VC++ MFC dialog application then it causes an exception in ctlnownd.cpp when you try to place the object in the application. I have kind of read on the web that this is a known problem but no one seems to say whether there is a solution to it. Without being able to include the debug version is another app it is proving very hard to debug it. Thanks for any advice you may be able to give. Andrew

Sorry, option 2 is the one I meant. When you pass in the HWND of the 'parent' window to the function, you attach this passed HWND to an internal CWnd object, and that CWnd can be the 'parent' for your internal dialog class. After DoModal returns and you collected up all the data, you can detach the temporary CWnd from the passed HWND. This way, the entire interface into the DLL to 'call' the dialog is a pointer to your data structure and an HWND. You only need to give the user a header file with the definition of your data structure and a function prototpye - the function exported from your DLL. I do this all the time to get InstallShield or legacy Win32 applications to be able to call MFC dialogs.

Hi I'm stilling working on this but have started a new post as the topic seems to have move on a bit. See DLL memory issue[^] post. Andrew Hoole

Oops. Sorry about that. Let me try again. Error message was error C2678: binary '<<' : no operator defined which takes a left-hand operand of type 'class std::basic_ofstream >' (or there is no acceptable conversion) Thrown by code void C3DPoint::Save(ofstream & s) { s << x <<" " << y << " " << z << endl; } With header #include #include using namespace std; class C3DPoint : public CObject { DECLARE_DYNCREATE(C3DPoint) public: . . . . int x; int y; int z; . . . }; Another error in a different source file is error C2079: 'file' uses undefined class 'basic_ifstream >' associated with code line ifstream file(dlg.GetPathName(),ios::in); Many thanks for any help. Andrew Hoole

If all this is in V6... I don't know settings in V7, then: Probably you have checked in project settings "Ignore default libraries". Try to add in libraries section libcd.lib (for debug builds) or libc.lib (release). The best way to detect such missing link symbols - at least for me - is to copy the offending symbol name, modify project settings to: - uncheck "Ignore default libraries" - check in Link --> Customize --> Print Progress messages and rebuild all. The linked with produce a verbose output wher you can search for the symbol. Usually, it will look like this: [Unsuccesful build] xxxxxxxx.obj : error LNK2001: unresolved external symbol _yyyyyyy [Rebuild with ignore default lib. off] Searching \.lib: Found __yyyyyyy Referenced in xxxxxxxx.obj Loaded DDDDDDDD.lib(DDDDDDDD.dll) Now you see that the missing lib is DDDDDDDD.lib; put back your project settings, add the new lib to Link section and rebuild. Usual trap libraries: - CRT: libc.lib (C), libcp.lib (C++), libcmt.lib (C multithread), libcpmt.lib (C++ MT) - msvcrt.lib (add a 'd' for debug builds, so Release uses libc.lib, Debug uses libcd.lib etc.) - COM support classes (_com_error) in comsupp.lib - Common dialogs in commdlg32.lib - shell API (shlwapi.lib) just to point some of (my :) ) usual mistakes.

Perhaps calling CWnd's CheckRadioButton helps?

Happy to oblige......... Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "But there isn't a whole lot out there that pisses me off more than someone leaving my code looking like they leaned on the keyboard and prayed that it would compile. - Jamie Hale, 17/4/2002

I don't believe your problem will disappear when you install latest service pack (SP5). It seems that you're corrupting the heap somewhere. I'd try to reduce the problem - create the sample MFC app with wizard, copy CROI and CVertexList, instantiate one CROI and fill it with multiple lists of vertices. If program will crash, you'll be sure that CROI the source of problems. To automate this kind of debugging you may consider a special tool, like BoundsChecker or Rational Purify. I'm not sure if you can download demo version of BoundsChecker today; evaluation version of Purify can be downloaded from www.rational.com Tomasz Sowinski -- http://www.shooltz.com

You've forget to select your DIBSection into dcMem. The first paremeter you're passing to CreateDIBSection is used only to initialize DC palette when you pass DIB_PAL_COLORS as 3rd param. Tomasz Sowinski -- http://www.shooltz.com

Just make sure you have the most recent service pack, and that should be fine. If you're still having trouble, then I would guess it's not anything to do with VSS itself but the project itself and your system. -- Where are we going? And why am I in this handbasket?