Nadya,

It's not the only way, but I think it's the best way... for parent and child to use separate business objects. And yes, the save only works on InitialSelectedAlias.

It may sound kludge-y at first, but each object is really designed to work with one back-end table... essentially a one-to-one relationship in that sense. And it should make sense. Each has its own data environment, rules object, etc. IOW, you can force the "square peg" into the "round hole" but I wouldn't suggest it... unless you're really into head beating.

---J


<snip>

>But since I got your attention, may I ask you another question?
>
>If I want to update two views, is it the only way to create two biz objects (parent and child)? The Save method doesn't work for every view in DE, it works with Initially Selected Alias, right? Or does it loop through all views in DE as ComCodeBook does?
>