>David,
>
>There is no precendence with and and or, they are evaluated from left to right with itelligent parsing in that the evaluation ends as soon as VFP has an answer. That is;
>
>a=.t.
>b=.t.
>c=.t.
>? a or b and c && nevers checks b or c because a is .t.

I more than suspect you are right. I was basing my comment on the manual which does show and with higher precedence than or.