Weird thing with VS (2005 at least)... If you aren't relying on DB data for your controls when you initialize them (which I learned not to do the hard way...) you might need to delete the bin and object directories from your solution folder. Close all designer tabs open in the IDE. Close VS. Delete those folders. Re-open VS. Recompile the app. Then re-open the files that were having problems. Don't know why this happens, just know this sometimes solves it.

Adding to led mike's answer, Preventing name collisions is the major reason for using namespaces. Nevertheless, the grouping of names for a specific purpose is a pleasant side-affect of this. Thus, for example, you can have elements that refer to schemas, html, xslt and xml in the same document. George

AutoScroll doesn't do what you apparently think it does. P/Invoking the Win32 API is also overkill. All you have to do is call the ListView's .EnsureVisible(_index_) method! Documentation[^] on ListView.EnsureVisible method Dave Kreskowiak Microsoft MVP - Visual Basic