Thanks for the link, great resource. I already knew about one of the combobox "workaround", but it's not obvious at first for the beginners like me. That said, even given the somewhat limited set of controls available in VS.NET, there are already a lot of third-parties fancy controls of every kind, so .NET is superior to VFP in that domain (but rich GUI has never been the strongest ability of VFP).

>Emmanual,
>
>PMFJI, I read your post with interest, as I do agree there is a considerable learning curve in going from VFP to .NET.
>
>I agree that subclassing takes many by surprise at first. But once you get over the surprise that you can't do it visually, it does become a good introductory exercise with the language and the framework.
>
>And the truth is, once you set up your subclasses, you generally spend limited time going back to them, so in time I've come to accept this as less significant than I originally did.
>
>On point 4, you CAN drop other controls (like a combobox) in a grid. You may want to check out http://www.syncfusion.com/FAQ/WinForms. This is an excellent site with a ton of good code examples, including several on grid handling.
>
>Yes, data binding could have been made simpler. No question. I wrote a generic binding manager and added some properties and a simple interface to my subclassed controls, so that all I have to do now is set 1-2 properties on each control, and drop them on a special entry container (sorry, 'usercontrol'...still having trouble getting used to the terminology) that takes care of all the setting, clearing, etc.
>
>Yes, I agree the winform designer generates more code than one would expect.
>
>Kevin