>I doubt if any quirks are due to reserved words, unless in SQL or View definitions. I use Type, Refresh, Requery, Date, and Value a lot, and observe no ill effects.
>The more likely cause of bad behavior is the improper use (or lack) of LOCAL, PRIVATE, and PUBLIC.
>
>
>>Answer me this please. I know it is ill-advised to use reserved words as functions and variables, but what are the consequences of say creating a procedure called 'refresh' or declaring 'isreadonly' as a private variable? I ask because I am trying to find the anomalies in an application delivered by others. The developer is a FPD/FPW hardcore (all SAY and GET, 200+ *.prgs and all free tables), but he put the program on VFP runtime. I want to find out if the quirks I am seeing are related to the inappropriate use of reserved words.
>>
>>TIA and wish me luck

There is no SQL or views, It is all seek, locate, scatter-gather @say-@get and the like. It is straight out of FPW/FPD, but uses VFP6 runtime. Fox doesn't do overloading, or does it?