Hi Kamal,

>I agree with you and I think it is the way the help file or documents which establish the relationship of the form and DE which is wrong (in a way).
>
Which I think is re-inforced with the samples (which I've never been terribly fond of).

>Taking an example users would never think of a form to have multiple DataEnvironments for a form.... Probably because their minds are tuned that way. Why would we need such a functionality is just a matter of design and encapsulation.
>
>The form uses all the DataEnvironments available for a private datasession. The CodeBook for e.g. uses a DataEnvironment for each business object and multiple business objects are dropped on the form. Which means that there are multiple DE's in the background. The form here is just a place for displaying information... like you said.
>
This "hits the nail on the head". Couldn't agree more.

>BTW, I am not promoting CodeBook here but it is just an example which I think was easy to explain. :-)

Didn't take it that you were. In fact, I think that this explanation of how CodeBook works is going to provide me with a good deal to think about, and perhaps be the source of some new ideas (or at least concepts).

Thanks for taking the time to respond to my post.