Hi Will,

Yes, I had the same question in my head. I answered myself with the *probability* that this was a problem similar to mathematical/rounding issue that comes up periodically.
But I must admit that I still wondered how there could have been 20+ of these records in the table as it struck me that there should have been an error on the first. ...On the other hand, rounding might explain that too - the info may be stored correctly (with different values) but being displayed as it is.

By the way, *IF* it is a rounding issue then I would like to see:
1) some warning of this possibility (which functions/commands/operations;
2) some programmer control over it.

Cheers,

JimN


>>You should use an integer as a primary key... you are taking too much of a chance that a user will not hit save at the same time. This is really an unnecessary risk.
>
>While I agree with all these responses about not using a date for a PK's
>Doesn't this thread strike anyone as a bit strange?
>
>Carol is basically doing a Scan loop, adding 1 to a variable and shoving that variable into a field and this is not working
>Pretty fundamental don't you think?
>
>Does this mean that VFP has trouble adding 1 to a Datetime value?
>
>Just my .02