>>
Hard to debug :) When some error happens that drive me crazy I prefer to test it with all "on error" routines cleared (just on error), set assert etc are all at their default. Exact line number is not shown and that's the problem IMHO. In fox2x days it was really driving me crazy for the point of error shown might be a read...show statement. Real error was something in @say,get or show routine.
>>I don't know. I never faced with an error with inkey() on my own. I searched the KB and found only one entry relating MAC.
>
>Have you used if inkey()=27 in your programs ?
>
>Put in into many places, distribute those
>programs to some hundreds of computers.
>Log all error messages into file using ON ERROR DO xxxx
>Look for this error and line number in those logfiles.
>
>I tried a make a test program which executes if inkey()=27 commands
>in loop, but currently cannot reproduce this error.
>I'm thinking about using KEYBOARD command to simulate some
>user activity, then using if inkey()=27
No, I don't remember an app of my own using inkey()=27 in many places.
Cetin
