We seem to be having problems with some of our customers who are running on networks losing data occasionally, particularly in the posting routines for our software. We are always locking the relevant records before writing to them, so we are pretty sure that isn't the problem. In order to test things out, we wrote a test program in our office in which two terminals consistantly try to lock and write to the same record. REPROCESS is set to -1, so in the event the other system has the record locked the other computer should continue trying to lock until it succeeds. Our system consists of serveral win95/win98 pc's networked in a peer to peer mode, but for this test we are using a Win95 pc as our server with one win95 client and one win98. Invariable we end up with one machine reporting a network error while running this test.

So with that background, I have the following questions:

1. Has anyone already solved similar problems and do they feel like giving us a little hint?

2. Is the problem here foxpro, the Win95 networking, a combination of both, or what?

3. Have any of you found that Foxpro 2.6 record locking works bettern on Windows NT or Novell than on a peer to peer win95 network.

4. Are there any other settings either in Foxpro or in the Operating System that we can use to try to fix this.

Our application is an "off-the-shelf" accounting app with over 700 installations, and most of these errors seem to be in out general ledger postings (which is a bad place to have errors for an accounting package, gee?), so we really need to find a solutions.

Thanks to anyone with any ideas,
Paul