Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
CDX is Updating, DBF is not Updating (sometimes)
Message
From
21/10/2006 16:14:10
 
 
To
20/10/2006 13:58:31
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
01163710
Message ID:
01163816
Views:
8
>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 less than 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???

Sounds like table corruption. A table can have subtle corruption and still be openable from VFP7. There have been several threads here from people who upgraded apps from earlier versions to VFP9, and VFP9 started reporting table corruption that had been previously undetected.

You could get a copy of your client's data, and:

- APPEND it to a known good, but empty table you have at your site (or rebuild the table from scratch with CREATE TABLE)
- rebuild your index tags from scratch

After doing so, test in their environment to see if the problem is fixed. If it is initially OK but the problem recurs later, they may have a network problem that needs to be addressed.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Previous
Reply
Map
View

Click here to load this message in the networking platform