Yep. Check SET COMPATIBLE and drill down through the affected commands/functions. Inconsistent at best.

>I agree.
>
>In fact, especially now that there are no more MS VFP paper manual, it would make good sense to FULLY DOCUMENT ALL COMMANDS that can be used in VFP.
>
>If they really want to discourage use of specific commands, all they really have to do is to say so, even using big bold letters if the choose, right above the syntax display for the command.
>
>
>>It is interesting to note that the "@...say" command is listed, in the VFP 6 help, as "included for backwards compatibility".
>>
>>For the related command "set device", OTOH, the full syntax is given, and no mention is maed about backwards compatibility!
>>
>>IMO, none of the two commands should be listed as "backwards compatible". While I personally prefer ?/??, @...say can be very useful to create text-files for different purposes.
>>
>>From the comments in the help system, it seems obvious that when they marked it as backwards-compatible, they were thinking about developing a form for interactive input with @...say, @...get and READ, but forgot about the other use of @...say: to create text-files.