Thanks for the info. Does this concern SQL and Locate and Scan also? I never use SEEK but I do use the others heavily. If it's Rushmore-wide then I guess I'll stick to ttoc() but if it's a Seek-only problem then I'l ignore it. :)

Then again, what about stored procedure logic for the DBC to always round the datetime to 0 miliseconds? Is that feasible? I just ran through my .chm's for Hacker's Guide and 1001 Things and didn't see anything about doing that but it seems like a good idea.


>
>One of the reasons for using the TTOC() is the following. VFP stores DateTime data to the millisecond in the DBF but we only have access to the second. If we were to SEEK a DateTime value of say {^2001-01-01 12:00:00} we may fail to get a hit even if there is a record that "appears" to have that value. Why? Because our value has milliseconds of 0 while the field may have milliseconds of 1 thus NO HIT.
>
>If the purpose of your index is simply to arrange records in an order, or if you only do searching in the index based on a range then this reason is meaningless to you.