>Tamar,
>
>>That could work. What I'm doing, instead, in a framework that's a work-in-progress is using the CA and DE together as the data layer and a Custom subclass for the BO. I have code in the base form class that ties the BO and the DE together.
>
>That is a much better idea, I believe. Since the DE and CA are really the ones handling the data stuff.
>
>Likewise, I am also into a work-in-progress framework. =)
>
>You think it is 'safe', OK and flexible enough to assume that my data layer deliver to me data in the form of cursors and that my BO only understands cursors?
>

I don't see why not. If you have a data architecture that promises cursors, why shouldn't the objects that accept results from the data objects assume cursors.

>What roles/responsibilities do you assing your BO? What I have put into it are:
>
>- record movement
>- record creation
>- data validation
>- process updates

I'm actually passing record movement and creation down to the CA/DE, though they pass through the BO.

>
>Anything I glaringly missed out that should be BO country?
>

Nothing jumping out at me.

Tamar