No, the Combo is in the parent form. And the table being modified in the child form is only used as a RowSource in the combo in the parent form.

>If I am not mistaken, this combo only cares about the table when it queries the contents. Call the combo's Requery method, and I bet you get a "Cannot access selected table" error.
>
>>AutoCloseTables is set to default (.T.) ... one main difference between your test and my app: While the table is opened in the parent DS, it's only used as the RowSource in a combo that is bound to another table.
>>
>>
>>
>>>>
>>>>Running VFP6 SP3: Have something really weird (at least to me) going on. I have a Form with a Private DataSession. It can launch a modal Form using the Default DataSession (it inherits the table from the DataSession of the parent Form).
>>>>
>>>>As an experiment, I changed the child Form to Modeless. Ran the application; opened the parent and the child. Went back to the parent and closed it. The child Form still works fine.
>>>>
>>>>What is going on here? I thought when I closed the parent Form, I'd get "table not available" or some other error message because the DataSession that opened the table is now gone.
>>>
>>>I just tested this on my VFP 6 SP3. The only way I got it to work without an error is to have [obviously] AutoCloseTables set to .F. in the parent form. I bound a control to the same field on both forms. When I switched back the the parent, it showed the data I had navigated to in the child form. I closed the parent and the child worked or failed based on the AutoCloseTables property setting. I did not bundle these 2 forms into an app with a Read Events.