#define MAX_LEN 255 CString str; char ch[MAX_LEN]; DWORD dwNameSize = MAX_LEN; GetUserName(ch, &dwNameSize); Best Wishes and Happy Holiday's, ez_way

I sent you a sample app with adding of elements. Let me know if this is what you needed. Thanks, Clay

Thankyou ohhhhh so much. Works now! cheers Bryce

CMessageLoop is a WTL class, and _Module has to have message loops added to it explicitly. IOW there is no API or method that says "give me some object representing the EXE's message loop" Also, _Module is per-module (thus the name), unlike MFC DLLs where several DLLs can share the same CWinApp object. So unless you control the EXE as well, the DLL has no access to the EXE's message loop. If you do control the EXE too, I guess you could pass a pointer to the DLL, although it wouldn't be possible to get to it in DllMain(); you'd need some other exported initialize function that the EXE would call. Now, if you create your own UI threads in the DLL, then you control the message loop and you can set up the CMessageLoop object like you want. --Mike-- Ericahist [updated Oct 26] | CP SearchBar v2.0.2 | Homepage | RightClick-Encrypt | 1ClickPicGrabber If my rhyme was a drug, I'd sell it by the gram.

The Windows Media Player SDK has an example of this called "WMPML" which can be downloaded with the SDK at www.windowsmedia.com It implements a big CAxDialog, but it doesn't compile! I haven't bothered trying to fix it, but it's probably what you're looking for. Ryan

Depends. If you're writing a COM client (ie you're using objects and passing BSTR values in), the general rule is that if you allocate, you must free. There's a _bstr_t (and a CComBSTR) type that is like a smart-pointer for BSTRs but it's not perfect. If you have a smart-pointer to an interface, then it will call Release on destruct. Non-smart pointers don't, so you should. You wouldn't call Detach unless you needed a raw interface for some reason. Steve S