>>>The main question I had/have is what actually happens on the line read events that it triggers an error. Since the application stays on this line for as long as the application works.
>>
>>In the pre-VFP days, there were people who used DO WHILE .T. as a wrapper around many routines. I've inherited a couple of applications where most of the code does that. I think it was bad style in FP2.x days and I think it's bad style now. (It might have been reasonable in the days before the foundation READ.)
>
>Perhaps you were given better info / had easier access to fox dev team. I found the documentation on fox read (valid) model probably the least clear and had to check myself for more than a day on basic working and genscreen result on stack and events. Read Events much better than foundation Read - but still not described well IMO.
>
>Too much "magic", not enough facts or at least descriptions for this doubting Thomas ;-)
>
>>I really, really, really think your problem is a flaky network. The fact that IIRC, only one client is having a problem strengthens that argument. If it were your code, it would happen everywhere.
>
>steady mentions like drops of water do not seem to register/weaken resolve to ignore...

Tamar,

I have reason for the loop. If the app closes - for many reasons - the loop is interrupted. The Cleanup methods try to cycle up all levels of open stuff (Form to modal form to report preview). The report preview could not be cleared by this, it must cleanup it self or the methods calling the modal stuff will fail (because they are like a parallel chain). So I crawl up until I gather something I can not simply release, order this to release via event and crawl all down to the loop, set a timer to try to close later on. This is simply cleanup says impossible to close now (try later). But this must run in events and is impossible to solve via procedural code. This is in fact a very cool way to kill the oddest modal crap down. So closing the app is as simple as CLEAR EVENTS - and then the loop will run by a timer until anything is closed. And the timer simply issue CLEAR EVENTS and disable itself.