To All -

We have had a Visual FoxPro 07.00.0000.9465 for Windows application in use at a client's site for 6+ years. All of a sudden, they are getting very strange behavior. It appears that every now and then, when they save changes to a record, the DBF is not updated. We audit changes to several tables using Update Triggers. The trigger fires. It might record a change of myField1 from "11111111" to "22222222". However when we look at the DBF, it is still a "11111111".

Even more interestingly, the CDX apparently *is* getting changed. If we issue a command like SEEK "22222222" it comes back True. We checked, and no other records in this table have a value of "22222222". If we issue SEEK "11111111" it comes back false.

Our Update Trigger writes a record to a free table for each field that changes. It shows this record as oldVal="11111111" and newval="22222222". Again, this is what we would expect for a valid change. However the DBF still says "11111111".

This only happens <1% of the time. The rest of the 99%+ time, records get saved correctly. If a record does not save correctly, all of the fields are left unchanged -- certain fields are not saved with others left unchanged. This is happening in several tables, and only recently (in the past few weeks).

We are struggling to explain this behavior to our clients. They are understandably upset.

Any ideas???