>>Like I said before, none of the frameworks I have heard about or seen have been really 'high-level' frameworks. Therefore, in my apps (which are consequently 10+ meg), if I had to worry about the extra overhead of somebody trying to solve every problem I could have with a table, then my apps would slow to a crawl. But they're fast right now, not lightning fast, but fast considering.
>
> What would you consider a "high-level" framework and what would it do and/or not do? What kinds of things are important to you, and have been important to your customers? If I'm missing something, I want to know about it ;-)

Things like being able to change the back-end and not have to rewrite a single piece of the middle-tier or the user interface. Being able to remove the user interface and not have to rewrite a single piece of the middle-tier or back-end.

Most important to me, however, is the ability to objectify data. The ability to provide a common standard interface in the data objects to save changes or revert them. By taking this approach, I can create COM objects for my middle-tier or compile them physically into the app because it won't change anything as far as the behavior of the middle-tier goes.