I have a site that is constantly getting currupt indexes on certain large transaction files from time to time. The problem is not persisant but happens often resulting in a lot of downtime to rebuild the indexes. Could u please suggest what the possible causes are or what steps should be done to elimiate this problem. We generally use the 'append from file' command to add records to the transact.dbf which has a number of index tags. The environment is Novel Netware 3.12 / Novel Netware 4.1 Windows 95 and MS client for Netware Applications are run in Foxpro 2.6b for Dos Run time. The latest service patches are used for Windows 95 and Netware. It is assumed that the users are not prematurely resetting their machines. Some super users access the data from Foxpro 2.5 and Visual Foxpro to reindex them when files are currupt. Using fpd2.5 may be problem as I recall fpd2.6 fixed a few bugs in it!!! The server did crash a few times. Any currupt tables where fixed using Visual Foxpro or FixFox utility. The server does incremental backups automatically. Could this be the problem with dual access to file? Overnight reindexing is done. I assume this as I have not verified this yet. What setting should be done on the netware side to cater for large foxpro tables. I remember Novell 3.1 had some problems? The patches fixed this. We generally use the 'append from ' command to add transactions from a temp file to the primary transact.dbf transaction file which has a number of indexes. The one tag 'auditno' constantly gets currupt. All replies welcome. Thank you. Gan