>

if a=b
>   c=.f.
>else
>   c=.t.
>endif

>
>I always use the short form personnally [c = !(a=b)], but I recently had to use the form you noted above because I was doing training and the other guy finds my "shortcuts" too hard to understand.

Too bad. The effort they'd invest to understand why does this work would return tenfold once they realize they've become more profficient.

It's probably my mathematical background that always pushes me to know the why, not only how. I have noticed this "this is the way you do it and don't ask why" approach in engineering studies; they even may know more maths than I've learned (well, in some areas), but most of them never had the time nor the inclination to look behind the curtains. That's why some of them end up knowing a way to do something, but that wouldn't do in Fox - it's at least three ways, or no way :)