Are you kidding? We've been through this before. My classes have no idea what a field is! They don't even know how to spell SQL. All of my database "info" is in custom properties.

With a totally dynamic interface, like the one I am creating, things are very different than with the ordinary layered approach. I am doing this to handle the volume of clients that we have and the volume of customizations that we do per customer. So my needs are very different than yours.

And there is definately a place for direct and specific data access code in the user interface, when you need to override the ordinary operations and make a form specific for a client.

In your model, how do you customize specific data code for one customer? Do you give them a separate EXE? Please let me know!

A little credit please, I've been designing and programming database systems since 1985 or 1986.

>>>>>>>>>>>>>Arrrgggghhh!!! You're not actually putting your DataAccess in your UI classes are you? Bad!