After really analyzing the login logs and the error logs, I've come up with some more ideas that I think might be able to help other people.
1. Make sure all antivirus is ignoring the data directories, the program directory and the temp directories 2. Turn off write-behind caching everywhere, the workstations and server 3. Turn of SMB2 and SMB opportunistic locking 4. Add FLUSH FORCE statements everywhere you change a field associated with a corrupted tag. I've added them everywhere and I haven't experienced a performance hit. After putting in FLUSH FORCE statements everywhere I do a record change inside the program, It seems to have solved the problem. I am no longer getting corruption errors, record out of range errors, index doesn't match table errors. I am not declaring victory for at least a month. The problem is when you're not really in charge of the hardware, new systems get installed and these changes don't get made. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
