It sounds like their indexes are getting corrupted. Make sure you have a reindex routine that deletes all the indexes and re-creates them from scratch.

Also, if their sever or workstations crash frequently that could cause the problem.

Also, it could be a problem with not enough file handles. If they're using Netware they may need to set the Netware FILE HANDLES= setting. I'm not sure how to do this under Win '95 (in DOS you just put a FILE HANDLES= line in the NET.CFG), but someone could probably help you with that.

Good luck,

Josh

>Those of you who have read my posts know I have been having trouble with strange things happening to one client, and only that client. At first, I blamed the problem on Win32s since they were the only ones using Windows 3.1. They have since upgraded. That solved some problems, but there are still some that remain a mystery.
>
>It occurred to me that there is a big difference between this client and the others. They have their tables on a server; the others, including me, have them on the local hard drive.
>
>The drive they are on is the F drive, so in the config.fpw it says "DEFAULT=f:\appl\tripsoft". It finds the tables fine, but I'm wondering if the fact that the drive isn't local is causing problems? Maybe the extra amount of time it takes to get the info from the server?
>
>The big things that are happening are "skip" not going to the next record and "losing" indexes. These are both table-related things.
>
>Have any of you experienced problems with running several local copies of the software with the tables stored on a server?
>
>If this is the problem, is there anything I can do about it? This really is a major problem. It's hard to edit records when you can't get the thing to move to the next record!
>
>Thanks,