Thanks, SK...that's very clear, though I do think that having anObject[i].Increment() behave differently according to whether anObject is an array of Foo vs. List when Foo is a struct is error prone. I actually think I would prefer that array indexing behaved the same way...that is, the indexer returns a copy. Now that I've had time to sleep on it, I remember that a few years ago I fought through creating an indexer for my own particular struct and came to realize that I had no choice but to return a copy...so I was getting the exact same semantics as occurs with List. Maybe I won't fall into the same trap again in a couple of years. But I wouldn't count on it! :laugh: cheers, jim

Ok, I think I've done all the manifest stuff correctly. DLLGetVersion on "comctl32.dll" reports Major Version 6, Minor Version 0, Build 2900, Platform 2. Here's the actual code fragment, since at this point, I think I must be missing something blindingly obvious: LVSETINFOTIP sit; sit.cbSize = sizeof( sit ); sit.dwFlags = 0; sit.iItem = 1; sit.iSubItem = 1; sit.pszText = L"fake primary info tip"; // This works, so we know item 1 is there. CString str = m_ListCtrl.GetItemText( 1, 1 ); // This always returns false, and no info tip appears. BOOL bResult = m_ListCtrl.SetInfoTip( & sit ); The extended style includes LVS_EX_INFOTIP and LVS_EX_LABELTIP, and I've tried either, both or none with no difference in results. Any insight would be greatly appreciated! thanks, Stache