>>Something strange happened to me last Saturday in
>>a case similar to yours. I was trying to update
>>a DATETIME field and the TABLEUPDATE() would always
>>fail. I changed the type to DATE and now it saves
>>perfectly. I see this as a bug in VFP 5, and
>>fortunately it is fixed in 6.0
>
>José,
>I am wondering if this is a Microsoft known bug? This is
>a concern to me because I was involved in a scheduling
>and call center project that as of today, has millions
>of records and is 500-700 meg. We never noticed (analyzed)
>or had complaints that the data was inconsistant with
>the real world.
>
>I'm wondering if I should warn the company.


I really don't know, because the app I'm speaking of has been working for 2 months without a flaw, then suddenly these TABLEUPDATE() problems arose. And with the customer data (nothing corrupt) I could verify it on my development machine too.

I found several issues on MSDN, but most articles are "How to". There is one about indexes that sounds interesting. I've consulted Q147587, 141084, 138980, 130346, 131254, 151755


José