I do the same with VFP as well and it works great (especially with VFP's OO capabilities). VB however allows me to move all business logic out of the UI into early bound DLLs. The UI thus becomes very despensible or interchangable. I have not tried this with VFP because I assume that late binding would perform poorly under such circumstances.

C#, great. Now more competition for us none C++ people. Looks like it is going to be a great product.

>I haven't go as far as dividing my business objects in UI and data parts because all code related to the way data is displayed on screen is let to the UI layer. My BOs give all the methods the UI need to display data and serve only to fetch, validate and save data from and to the database. My BOs doesn't need to know how the data is displayed.
>
>I use mainly VFP to build my apps, so I don't concern myself too much about early vs late binding performance. I've used VB to do some specialized stuff like communication and scale COMs.
>
>You can get more informations about C# at http://msdn.microsoft.com/vstudio/nextgen/technology/csharpintro.asp