>I want to understand what I need to do to make the transition into stateless COM objects for my business classes. There are many situations where an lAllowInsert, lAllowDelete, or lAllowUpdate are predicated on the evaluation of business rules separate from user specific rights.

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.

>I have to admit I'm kinda slow in grasping some of this stuff. It will probably come to me the same as OOP - frustration... more frustration ... then BAM like a bolt of lightening.

Actually, it took me a while, and thinking stateless was more a gradual process of getting out of the habit of thinking stateful. The process is forced with any kind of web development, because all web code is inherently stateless. But getting used to this was tough for me- I had a couple of times that I got caught relying on record pointers and whatnot between calls, and was left scratching my head until I realized I had violated a 'stateless' rule.