Hi Bob ---

Try this: Why not just open the table in the Load event of the form if called from the hotkey and forget about the Data Environment?? Set a custom Form property accordingly and check that property at QueryUnload to see whether or not you have to close the table.

>
>My parent/child is the usual order/item combo. The twist is that the item edit form (property sheet) can be launched from 2 spots. One spot is from the order edit form, as discussed. But, the user can also hotkey to it from another spot (a different list).
>
>Could the item edit form define a private datasession, but set the form to use the Default Data Session (so it works from the order form). Then, if the form loads from the hotkey, change the datasession property back to Private Data Session to get the datasession stored with the form?