>>>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
>>
>>Often you can get away with things but you will be sorry later. It is better to not use reserved words. I have seen applications run for up to six months and then refuse to work again for reasons such as this. Avoid problems when possible. :)
>>
>>Tom
>
>To all,
>
>I know it is not right. Before I go to the developer and tell him that I think this is the problem, I'd like to know some specifics. He has good problem solving routines, but just can't grasp visual programming and the wonders of the VFP environment.

Well, this project sounds like a "conversion" from FP 2.X into VFP. Did it ever work? Such conversions are a mixed blessing. If you ever want to modify, add or debug you are going to pay a price in time. The purpose of VFP is to reduce maintenance and development, while allowing the possibility of using newer programming techniques and functionality. These conversions can be a serious issue!

Tom