>>snip
>>>
>>>If a foundation read was being used, the typical procedure was to assume that the user had closed the window from from the close menu in the upper left hand corner unless the window was participating in the current read. This would cause any clean-up code to be executed. If this included code to close any tables that the screen had opened, it would explain what you're seeing.
>>
>>Thanks George, but that's not it. No Foundation read in this (instance)(case)thingy. (Too many key words) Just plain miserable coding. Everything else SEEMS to be okay, and the window does come back on OPEN WINDOW at the end of my prog.
>>
>Pete,
>
>In the Debug window, enter the expression USED(< alias name >) and click the bar to set a break point after the window has opened the file. When it changes the execution should stop and you should be able to see what closed it (CLOSE ALL??) by issuing ACTIVATE WINDOW TRACE from the Command Window. Be sure, however, that all source files are on the fox path and the program, if compiled is up-to-date.


OK guys,
that's what I'm doing now.

PETE