Try opening Visual Studio with elevated privileges. «_Superman_»  _I love work. It gives me something to do between weekends. _Microsoft MVP (Visual C++) Polymorphism in C

Try posting this in the COM forum, so one of the COM wizards can see it. Unrequited desire is character building. OriginalGriff

dybs wrote: Does this only apply to the Enabled property of controls I don't know; I don;t think it is documented, and I don't need to know as I keep my handlers short. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] I only read formatted code with indentation, so please use PRE tags for code snippets. I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).

Hence you have loaded object path conflicting with registry one? I'm sorry but can only suggest you using Oleview tool to get additional info. :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke

sandeepkavade wrote: but how to execute that through code? [Starting an Interactive Client Process in C++^]

If you look here: http://msdn.microsoft.com/en-us/library/ms690368(VS.85).aspx[^], you'll see: MSDN says: Notes to Callers You should not have to call DllCanUnloadNow directly. OLE calls it only through a call to the CoFreeUnusedLibraries function. When it returns S_OK, CoFreeUnusedLibraries frees the DLL. You should call CoFreeUnusedLibraries after unregistering it. Also make sure that you have no live COM objects created by the DLL. If not, the DLL will have a reference count > 0, meaning that DllCanUnloadNow will return S_FALSE. It could also be the case that reference counting in the DLL is buggy. -- Kein Mitleid Für Die Mehrheit

Check why the Impersonate to other user is not successful.

You could always try TinyXml and compare the two approaches. That way you'll know which is the best for your situation. "Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Is the event interface defined as a dispinterface or a dual interface? It ought to be a dispinterface, really - I think dual interfaces can cause access violations (which is what your error looks like) if used as an event sink. I'd also suggest adding the following two lines to your stdafx.h before any ATL files are included. They will show (in the debug output window - you need to run your application with the debugger) when AddRef/Release and QueryInterface are called, which may help you debug your issue. #define _ATL_DEBUG_QI #define _ATL_DEBUG_INTERFACES

You might want to ask this in the Visual C++/MFC forum[^]. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007

jhwurmbach wrote: According to the link[^]given in the posting below, UTF-16 is fixed 16-bit Don't know about the link, but UTF-16 is definitelly not fixed 16-bit per character. There are surrogate pairs[^] that cover the space above 16 bits. On the other hand, with UTF-32, each code point is encoded with a 32-bit number, and it is the only fix-length Unicode encoding schema. Programming Blog utf8-cpp