Hi Nishant, The article is now available Thanks, Sean Ewington The Code Project

nbugalia wrote: When I am using ListControl on the dialog, the dialog is not becoming visible. Can you elaborate, please? :confused: "Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

My friend Google knows[^], he even refers you to CodeProject articles! :) Luc Pattyn [Forum Guidelines] [My Articles] this months tips: - use PRE tags to preserve formatting when showing multi-line code snippets - before you ask a question here, search CodeProject, then Google

The below code is from MSDN. While their samples can be lacking sometimes, they're not usually wrong. if (pmyTreeCtrl->ItemHasChildren(hmyItem)) { HTREEITEM hNextItem; HTREEITEM hChildItem = pmyTreeCtrl->GetChildItem(hmyItem); while (hChildItem != NULL) { hNextItem = pmyTreeCtrl->GetNextItem(hChildItem, TVGN_NEXT); pmyTreeCtrl->DeleteItem(hChildItem); hChildItem = hNextItem; } } The only thing I can think of that may mess it up is if your parent item does not actually have children in it, but you've manually set its item.cChildren to I_CHILDRENCALLBACK. Can you check the return value from ItemHasChildren to make sure it's 0 or 1? Iain.

Please Note: _rmdir The directory must be empty, and it must not be the current working directory or the root directory.

Firstly, as already mentioned, CoCreateInstance uses the IClassFactory interface to create the object. Secondly, IClassFactory has other methods besides CreateInstance. Finally, the class factory is allowed to implement other interfaces. Steve

In both cases, the parent or owner has been set as the parent of a control (e.g. SetParent(), or by specifying in the parent parameter of a Create() call). The difference is that if the control was created with the WS_CHILD style, then the outer window is a PARENT. If it was created without this style, it is only an OWNER. For a parent window, when the parent is minimized all child controls are hidden. For an owner only, 'owned' windows remain in place and can be minimized separately. Note that only 'windows' can be owned - 'controls' *must* have a parent and are therefore created with WS_CHILD. (GetParentOwner() will find the nearest window that is *either* a parent or an owner, but not a child - the others will keep walking up the chain until they find specifically one or the other.)