Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Automated verify and check for curruption without invoki
Message
 
 
À
28/03/2001 10:59:55
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00489458
Message ID:
00490742
Vues:
8
>Is there a product or technique that would allow for policing curruption (database, tables, etc) in an application without having to handle them as a support call by the user. I have't invested in any 3rd party product yet, but am being killed by the frequency of having to recover something related to data several times a day (pc lockup, VFP freezing etc).
>
>Is the developer community being plagued with data curruption problems in the real world or am I missing an important piece of information.
>
>Any solutions or advice would be greatly appreciated!
>

I am in the process right now of adding FoxFix 5.0 to my application. They have a Steath mode which checks for header damage in memo, dbfs, and indexes each time a table is opened. It can repair most header damage. If it can not repair then you write some code to errormessage, write a log, etc. Unfortunately I am out of time and unable to fully implement the Stealth mode and am settling for a DO WHILE through my DATA folder each day when the client performs a specific task. I write out an error log and give an error message when Foxfix could not fix the problem. Bundled with FoxFix.dll is a FoxFix5.exe and a DataScan.exe. The FoxFix5.exe does a more thorough scan of header type data and DataScan.exe is very slow running, but it data a datascan. There is also a product called Stonefield (or something like that) that is suppose to be good also.

I know that Novell is a problem with VFP. I have many corruption problems and I run Novell. And many times my corruption is data corruption which FoxFix I do not think will detect. I will find out after it runs in production for awhile. I now looking at my ON SHUTDOWN to make sure I properly close files and adding a FLUSH after updating to make sure the data is written back to the file and not just residing in the buffer. I have also read here on UT about doing buffered updates, but my app is big and I have no time to fix and test that. Craig Berstien, or something like that, has a corruption checklist on his site and steve black has a corruption checklist (appears somewhat dated but give you some ideas).

You can do finds here on UT on FoxFix (you will see my name on many of them), corruption, novell, shutdown, and flush. trying doing a search on corruption on the download site.

Brenda
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform