>>Today I would use Keypress or Interactivechange. I used this approach long before OOP was implemented in VFP.
>>
>>BTW, "there are no stupid questions, only stupid answers".
>
>And then there's the magical word "doh" and the magical slap on the forehead ;).
>
>The stupid clause doesn't apply to this case, because many of the workarounds for bugs (in either Fox, VFP, DOS or any of them Windowses) may look really mysterious if you don't know what the bug was. The chr(255) was probably an internal way of messaging (IOW, I too don't really understand how it worked and why it was needed - I know mine didn't need it ;). Stuffing special characters into the keyboard buffer so they'd produce a special return value from readkey() was a technique which worked ever since FoxPlus, and only got additional values in FP. I now have trouble trying to understand my old code which used that, despite all the comments I wrote :).

I can't even understand my comments I wrote 3 weeks ago. I was working today on a code that I wrote only about 3 weeks ago and it took me about 5 minutes of reading my own comments over and over until I got it. I think writing good comments is like being a good writer in general. And only a few have this talent. (I am just trying to console myself <g>).