Thanks Kevin for prompt reply.

> At times its desirable for forms to have their own copy of a business object

Like when two forms need a different 'current row' in the same dataset for instance.. <g>. I'm sure also that if I really wanted I could implement some kind of "bizobjmanager" object analogous to FormMgr. I can't immediately conceive of a generic need for this.

I'm going to have to solve this one in a couple of days, but most likely by sending messages. Whether I actually need to implement a FormMgr.Broadcast() method or something else, I'm not sure. I'll probably throw something together that only just works: in nearly every case I have modal edit forms opened directly from a view-only form, so it is pretty easy. I've only got one situation (in this app) where I'd like two modeless forms sharing the same data, and at worst I'll just have to make every form explicitly aware of the other one.

> Subcategory relations

eg create table party ( partyid, name, ...) create table customer ( partyid, more-attributes-apply-only-to-customers ), the answer is probably "create stored procedures for data access". And then ignore whatever the wizard generates

I have to go, I'll continue pondering