>Fabio, 'reserved word' means that using such a word for user-defined entities is not permitted. It does not mean that Fox is required to warn you when you violate that rule, it means that if you violate it then all bets are off and the result is undefined. The actual result could be anywhere between 'works as expected' and 'blows up in your face', and it can easily vary between versions and between service packs.
>
SNIP
Pardon me for jumping in, Stefan, But when was it that you were appointed the governor of error messages and when they are to be emitted?

I can tell you that in many languages, possibly most, the use of a RESERVED WORD does cause an error message to be emitted. It really is the ONLY practical way to assure consistency while avioding the infamous "unpredictable behaviour" result that is too often stated for too many situations.
Some languages even provide a means to circumvent to the problem to protect backward compatibility (like using a prefix 'escape' character or some other means) though in such cases it does require progr changes to remedy the problem.

That VFP has to date ignored the issue does NOT make that the correct approach, no matter what rationalization one might try to apply. And if backward compatibility is really the concern then they could offer a SET to make enforcement optional.

cheers