Currently, my bizobjs have cursor state properties (e.g. lCursorModified, nUpdateConflict, lCursorEOF, lCursorBOF, lAllowNavigate, lAllowDelete, lAllowAdd... etc.) which change via rules in their _access methods and are queried as needed.

While I haven't had the time to do so yet (have'nt had the need yet, I need to come up with some sort of mechanism to retain cursor states - maybe a state object with the corresponding cursor state properties and SetState() / GetState() methods.

Don't know yet - just thinking out loud.

>Jeff,
>
>Stateless objects aren't the pits, it is the way we think about data that causes the problem. For example we seem to always think about table navigation, next previous and stuff like that. Well in a stateless world you can't do that because the middle tier has no idea or reference to where you were the last time you called. Things have to be done through passing a parameter that tells the middle tier object what to laod and where to point..
>
>This ia a major reorganisation of how systems should work. It is analgous to the problems wrestled with by developers moving into C/S the first time and they wonder why their SELECT * FROM Customer BROWSE is so slow.