>>
>>The behavior of the count as to know wether or not if will fire an error is unpredictable. This is what I came up with.
>>
>>Also, when it goes into the error handler, it will proceed on the code as is and will ignore the RETURN TO clause.
>>
>
>Michel,
>
>I have found that the error will not fire if the currently selected table does not have any records. IOW, VFP is going from left to right, and never looks at the FOR statement because it knows it is going to return zero records.
>
>Is your CONTACT table populated with records?

You're right. I just added a record in a test table and I got the error. Yes, Contact does contain some records. So, this is why we got the error.

But, on some occasions, we might issue a COUNT on an empty table. So, we need to find a way to force the error to kick in every time.