Hi!

I guess it is depended on the internal VFP logic and it is quite hard to tell about behavior of VFP in such case. Just use of rererved words is not recommended, however, this does not means that every reserved word will cause error for sure. Just inpredictable behaviour.

BTW, in addition to what Alex said about DESCRIPT, in our databases we usually use type prefix for fields (naming conventions) either in VFP or SQL Server database, so our field in such case will look like 'mDesc' that eliminate most if not all problems related to reserved words.

>As someone found the logic of VFP when using a field name DESC in a SQL? Sometimes, the same SQL will generate an error if a field name is Desc. Most of the times it'll work.