Table Corruption

We seem to have a reoccurring problem at just one of our client's offices. There are two tables (both have a key field) that have become corrupt about once a month for the past three months. We have successfully repaired the tables by using the table repair utility. Both of these tables are used heavily on a daily basis. Each time our research has shown that the time stamps of the original .db & it's .px file are out of sync. What would cause this? Our suspicions are network connectivity issues, however, how do you prove this sort of thing? We're considering removing the key field in order to eliminate the .px's but I'm not sure if that'll do the trick.

Background info: Paradox 10 application being used on Windows NT systems.

Any suggestions?

Hey Tony, do you have the link to a white paper on the Opportunistic Locking and Write Behind Cache issues? I need to give it to my NW Admin so this can be properly implemented.

Mac

[i]"A king will have his way in his own hall, be it folly or wisdom."[/i] - Gandalf

I would make sure of 2 settings on the server storing the data, as well as all workstations that access the data.

Opportunistic Locking and Write-Behind caching.

Settings are most important on the server, but should be turned off on both the workstations and the server.

http://www.tonymcguire.com/oplocks-2000.htm
http://www.tonymcguire.com/oplocks-nt.htm

I set these up as easy *self* help to get to them quickly.

They also contain a link to the M$ papers.

They have the settings for both workstation and server; make sure you use the appropriate one, cause it DOES make a difference.

Don't have links for the write-cache stuff. Basically, it is a property of your hard drive(s).

Back to the original question:

It may sound *real stupid*, but I would also make sure any cutesy (any, really) screen savers are removed. As well as participation in any of the 'use my computer when it isn't active' programs out there (SETI, for instance).

Also, I disable ALL power saving features. Workstations AND Servers.

They may all be nice to have, and wonderful things to have/participate in, but they don't belong on a system running database software.

I'd be REALLY interested to hear if any of these turn out to be culprits. Since disabling this stuff on my systems, I don't have a lot of the problems I see reported here and on newsgroups I participate on.

Are the networks clocks synced (sp?) together? Are you haveing problems with .lck files also?
When you repair them and you look to make sure everything is "OK" again. Are there errors in the tables?

I know i am mostly asking questions, i find those very helpful when solving my paradox issues. Also there windows temp directories may have excess garbage.