I understand your questions, I have been though them all.

First, I have hacked together a application that builds the classes for me based off of the database tables. This saved me a bunch of time. I am updating the application and I am making it even more powerful. When I move it to the beta stages, I will send you a email and let you try it out and tell me what you think.

Next, you REALLY need to look at the Data Access Block from Microsoft. They have already written all the SQL data access code you are saying you have built/are building. You can find it at: http://msdn.microsoft.com/library/de...ml/daab-rm.asp It is just plain awesome, and saves a bunch of coding. I am centering my tool around this access block because it is a known constant.

Last is you expose your custom collections as a property of the parent class. For example, think of these forums. You have a parent object for the thread. It has the basic information about the thread and the initial post. That thread object contains a property that exposes a collection of reply objects. Then, you do binding to these objects.

You would be suprised at how much coding you save when you standardize on some basic things. After I finish the code generator, you will see just how much time it saves. I can build about 80% of my business layer in about 15 minutes. That is just awesome. The majority of my time is spent just hooking up the UI layer to the business layer and controlling user interaction.