[RESOLVED] Nearest Minute Causing Duplicates in PrimaryKey of Date (Access)

[dw85745]

FunkyDexter:

Re: Design Issue: Program works great since 1994 -- other than an infrequent problem that is uncovered (this post case in point).

You've said you're not updating the primary key but it looks like you are:-
!fldHistDateTime = dtmDateTime

GOOD CATCH. Have remmed this line under EDIT.
Dumbfounded that I missed it. Oh Well!!!!!
FWIW: Just went through my code and found 3 other PrimaryKeys (datetime) I was Editing.
Forgot to Rem or delete when I copied block from the Add code. THANKS.

Re: Precision.

I don't believe formatting the date will do anything to the underlying DateTime double which is what is actually stored. Will VERIFY.
On my system a DateTime converted to a double shows up with a precision of 10 decimal digits.
All decimals are filled no matter whether formatted to hours, minutes, or seconds. Access (to my knowledge) does NOT handle milliseconds.