Hi Jim ----

Nope, there is something else at work here. Remember the thread a few months back where a SELECT - SQL statement involving Datetimes wouldn't work as expected either? I just created a table with 100 records with random DateTimes. Was able to seek one particular record in Command Window with SET EXACT OFF. Stored my successful SEEK value to a .MEM file. Then created a small executable that did essentially the same thing with the same environment and FOUND() was .F.

Therefore, I go back to my earlier assessment: Use TTOC() in the index expression and in the SEEK expression.


>>
>>We have seen this one before. There seems to be a problem with SEEK and datetimes.....the solution would be to use TTOC() in the index expression and the SEEK.
>
>John,
>
>The problem is that DateTime is stored with an resolution to milliseconds, but we can only access to seconds, therefore there is little possibility that the value we seek will exactly occur in the data. SET EXACT OFF and SET NEAR ON may help with this.