>Hi,
>
>sorry for the cross posting from the general thread. but I thought that this would be a better place for my questions.I have a piece of code that goes like this:
>---------
>WHILE !quitevent &&main event loop
> DO CASE
> CASE menuevent
> DO p_menuevent with ...... && process menu event
> CASE windevent
> DO p_windevent.... && process window event
> OTHERWISE
> READ VALID fndrdval() &&foundation read
> ENCASE
>ENDDO
>....
>....
>FUNCTION fndrval
> windevnt = .t.
>RETURN
>------------
>What is the use of READ VALID as compared to READ EVENT?
>I did some tinkering of my own (unfortunately my code is too
>large and involves too many files to be posted here) got stuck at the READ VALID statement. The tracer will be stuck at READ VALID (looping over and over again at any knypress/mouse click) and then upon chancing on READ EVENT, I decided to try and my some freak chance,I got the whole code working.
>
>Anyone has any ideas? Anyone encountered this problem during porting a FoxPro program from DOS to Windows?
>
>Helpless
>Ian

Read valid and read events are totally different (except names). In short I could say "read events" is something like saying "OK puzzle is ready for you, now go and process and come back here when you find a *clear events* somewhere then I'll let you go down the code and it's also your only ticket for liberty".
No more use of FP 2.x read - in practice, otherwise ported screen have read* properties (and if I'm not wrong, only "read events" which is similar just in name).
My practice on porting apps to VFP is writing them from scratch.
Cetin