>A critical problem holding up an upgrade:
>
> Background: We've been getting ready to move from FP 2.6 to VFP on our accounting software (SBT).
>
> This requires "bringing along" another large app with a Foundation Read. I've been directed to do "minimal" work on it (let's call it the MAIN program). I've found that simple windows get removed fine with RELEASE WINDOW window_name, but on Parent windows with Child windows, when I "RELEASE WINDOW window_name", no matter what I do, the window remains in memory, even after it has passed the RELEASE WINDOW point in the code. (Remember, when running Visual 5.0)
>
> If I go to the Command Window, and type either RELEASE WINDOW window_name or CLEAR WINDOW window_name, the window is cleaned from memory, but it is not cleaned during running code.
>
> Since the code logic (I didn't write it) branches on condition of existing windows, I have to find an API, I think, or some other active method of removing the Window information sitting in memory.
>
> Thank you for your help.

Hidy Tom,

Try using this, after loading foxtools:

* screen caption, of course, should be replaced
* by a string
lnwhandle = _WFindTitl(screen caption)
= _Wclose(lnwhandle)

You'll find more information in my Extended Foxtools Help file.

hth,