Mark,

I just want to point out the "child" form doesn't have to be modal. If the child form's DataSession is set to Default and it's launched from code in a Private Datasession form the child form opens in the same Private DS and has access to all the tables already open and any that it opens are added to the PrivateDS.

I'm using this heavily in an app currently in development. It lets the child tables get the PK of the parent table and do things like set their captions based on the cName field of the parent.

>Let me make sure I understand, Barbara. If I set the second form's DS to Default, then it uses the DS of the caller, even though the caller isn't using the Default DS (i.e., DS 1?). Or are you saying I shouldn't populate the second form's DE, and set DataEnvironmentID to the caller's?