>>>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 agree that the initial descriptions felt like magic. But between discussions in the FoxForum and articles in FoxTalk and trying it out, I made sense of it. That said, for sure, the introduction of READ EVENTS made things much easier.

Tamar