>>you don't get any errors, until you run the prg. There are other tools which do a better job in *checking* snippets, tables, etc. before a problem is found much later, as was the case with my table including a field named *left*.
>>
>>FWIW, Kim
>
>Kim:
>
>I absolutely agree with you. I spent several hours chasing a problem that turned out to be my usage of a VFP 3.0 reserved word (newly reserved in VFP). The help screen of reserved words produces a pretty lengthy list of words. VFP 5.0's color coding helps, but every other language I've worked with catches things like this *before* runtime . . . .
>
>John

There are some problems with VFP 3.0 complier catching things. The VFP 5.0 compiler has been tightened up and catches many more bugs than 3.0.