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

---

>Hi Sylvain. Do you divide your middle-tier into UI-Centric (client side) and Data-Centric (server side) business objects? If so then if your UI-C BOs are responding to KeyBoard, Change, etc., events from the UI then would early binding not be critical to performance? Or I guess in any case where your UI uses your BOs extensively?
>
>What is C# ?