>Fine, but these facts need to gathered in their own method call done before the Add or Delete attempt. I guess I could make a clearer strategy recommendation if I better understood a situation that would dynamically change a client's ability to Add or Delete a record.

A floor of a building has 500,000 sqft of rentable space which can be configured to any number of suites of any size. A new record is created for each suite and assigned a sqft number not to exceed to remaining number of sqft. After all the footage has been assigned, no new suites can be created - hence, no more inserts.

Say the above example applies to booth space for a trade show and you want a road team out there selling variable footage booth spaces in real-time over an Intranet.

There are unlimited examples of business rules which apply to inserts and deletes. I have yet to do any Web development, but the-time-is-a-coming real soon for some challenging Intranet stuff and I need to see what changes I need to make to my framework to accomodate it as well as to work with another framework like WW in addition to just plain grasping this shit.