>MyTable.Counter1 (integer)
>MyTable.Counter2 (Numeric 4 0)
>
>REPLACE MyTable.Counter1 WITH 1
>REPLACE MyTable.Counter2 WITH 1
>
>DO CASE
> CASE MyTable.Counter1 = 1 && is unreliable?
> CASE MyTable.Counter2 = 1 && is unreliable?
> CASE MyTable.Counter1 > 0 and MyTable.Counter1 < 2 && is reliable?
> CASE MyTable.Counter2 > 0 and MyTable.Counter2 < 2 && is reliable?
> OTHERWISE && just in case :-)
>ENDCASE
>-------------------
>
>And if I remember correctly VFP does not handle LARGE numbers as well as it implies (granted in this case zero is not large)... as is illustrated in "Hackers Guide" on page 15...
>A numeric field will contain a 20 digit number but Microsoft describes accuracy to 14 or 16 digits....

Richard,

Integers, Doubles, and Currency won't be a problem as they are stored in the dbf exactly as they are in memory. Numerics and Floats are where the problem lies.