Fred,

Yeah I ran into while working on a knitting mill system that did the data gathering in C and was giving me datetimes with milliseconds and they made it out to the dbf just fine but we ran into a couple of minor analysis issues because of it.

>I just thought it did then, I guess. I've heard there were problems in a SQL SELECT on a datetime value. Kind of like adding a decimal value instead of an integer to a date:
>

>d1 = DATE()
>d2 = d1 + .05
>? d1, d2   && both print the same value
>? d1=d2    && .F.!
>

>
>The date values will strip off any of the excess when written to a field. Drove me nuts in a scheduler I did years ago when two date variables wouldn't compare!

For scheduler sorts of systems I've taken to just always putting future events into a queue and when the scheduler fires up it just always pulls things that have not been processed and the event time is less than right now.