>>
>>In VFP7, does it fire the error on a table that contains a field named IRegion? IOW, did you run a COUNT FOR x=y statement against a table where the left side (x) was valid, but the right side (y) was invalid?
>
>Sorry, I was wrong. It works the same way as in VFP 6.

Part of the craziness is caused when the table is empty...the error does not fire because VFP does not need to inspect the FOR clause.