Reoccuring Table Corruption Problem

[WMXTeam]

We are having significant corruption issues with two of our tables since October 2006. The two most prevalant issues are either deleted records displaying even though Set Deleted On has been issued or the indexes getting corrupted. When we pack and reindex, the table is fixed temporarily. However, the corruption issues reoccur within a couple of days. We have even tried creating the table from scratch and inserting the records, but this did not fix it.

The tables are used by a Foxpro Windows 2.6 app and a Foxpro DOS 2.6 app. Most workstation are running Windows XP. We are working on upgrading all workstations to XP.

Has anyone else experienced this kind of problem? Any and all input is appreciated. We are very frustrated.

 

[cricket]

You should describe your network in order to get best suggestions.

A couple of points to start with:
1. Operating system unlikely to be the issue
2. You might have SET DELETED ON in your program code, but then open a VIEW which has the opposite effect embedded in it.
3. Network cabling is a possible cause of corruption

 

[dgrewe]

Had a problem similar to your corrupted Index some time back. It was a Bad block in the hard drive and when the system wrote to it Fox reported a corrupt index.


David W. Grewe Dave

 

[TamarGranor]

I had a client who had files that kept getting corrupted due to a printer driver. Did you change any printers in that 10/2006 timeframe?

Tamar

 

[WMXTeam]

Thank you everyone for your reponses.

As requested, our network engineer has provided the following details about the network:

We are one domain in a multi-domain model. Single forest.
Users who access data are either local or connected by t1 or better at a remote site.
DCs = Microsoft
File Servers = Netware and Microsoft
Use CIFS to access windows files when no netware client is being used.
Most users use netware client.
Multiple VLAN but all Vlans are accessible to other vlans.
Workstations range from DOS, win98, win2k, winxp, winxp64.
OS version Netware 6.5 SP6 (file server OS)
Mcafee version 8.5.0.781 with DAT 5154

 

[pthalacker]

Novell and Fox never got along. There were times when my Novell client would keep a file handle open even after I closed Fox. It required a cold boot for me to release the file handle. This is a recipe for table corruption. Running FoxFix was part of my weekly maintenance routine.

The situation was much improved when I converted the existing applications to use VFP views and native table buffering.

pamela

 

[cricket]

My experience of Novell is diametrically opposite to pthalacker.
If a server has been up for many years non-stop , the risk of corruption is greatly reduced. Novell is rock solid for Foxpro

 

[dgrewe]

Actually both of you are correct. In the Novell 2 & 3 days there was a problem with FoxPro correpting Database files. Novell fixed it in the early Novell 3 days. There was a fix that required a setting to be changed from it's default. I used FoxPro & Novell from 1989 to 1997 and never had the problem after version 3.


David W. Grewe Dave