>Could it possibly be that code depends on a holdover from FoxPro days where sometimes you can have an implicit && comment (which I recall often occurring with IF statements) ? Basically something like:
>
>

IF 1=1 AMD 2=1
>    ? "Yuck!"
>ENDIF

>
>rather than getting a syntax error, the mispelling of "AND" would cause an implicit && comment, so that the code would execute as:
>
>

IF 1=1 && AMD 2=1
>    ? "Yuck!"
>ENDIF

>
>In VFP 6.0 the FLUSH command lacks the additional clauses available in VFP 9.0 (don't have 7.0 nor 8.0 so I don't know in which version the additional clauses for FLUSH command were added) -- so the particular example of the FLUSH command will not generate error (i.e. the "!_ERR=0XCA" is completely ignored).

I guess everything is possible, but it depends on which VFP version the program in question was compiled with. I think it was from VFP8 that most "typos" which earlier were accepted or ignored, started to raise errors.