Bob ---

Save yourself some grief and avoid the mess of passing around DataSession IDs...

>I came up with one other suggestion (comments/criticism appreciated):
>3) create a private datasession for the child, that contains the tables needed when launched w/out the parent
> pass the DataSessionID from the parent to the child
> in the child init(), change the DataSessionID if a new one is passed in
> PROS: a single form, both datasessions are visual, no code
> CONS: the docs says changing IDs should only be used for debugging (ouch!)
>
>Bob