Tables can only be corrupted when they are being written to. If your POS system has a flaky power source, or a bad LAN connection, or users who pull the plug on it, it can get corrupted if those events occur during a disk write.
You can switch to table buffering of your table, along with specific TABLEUPDATE() commands to localize the disk writing to specific points. If your app edits the data directly, each edit is a potential source of corruption.
Hope that helps!
-- Ed
-- Get great VFP support in a new forum filled with Microsoft MVPs!
--
Forgive me if this is obvious, but the best way to avoid corruption is to find out why the corruption is happening in the first place.
Can you localise the cause of the corruption? Are there any common circumstances that apply? Can you say what the nature of the corruption is (bad DBF headers? corrupted index? )?
If you can get more information, it might make it easier to find a cure
Mike Lewis
Edinburgh, Scotland
You say you have UPS on the workstations, but you don't meniton the file server. Even if you are using a peer-to-peer network, you should have a dedicated PC for the file server. Ed's comment on the network hardware needs to be emphasized. Have you tested the network connections, hubs, NIC, cables, shielding? Are you seeing any network errors or excessive retries? As in most "systems", it's only as strong as it's weakest part.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.