> We are experiencing network related error messages as more and more > users > use our app. The error messages are: "Attempting To Lock..." and > "Record > Not Available, Please Wait..." What's happening here is that one user has the record/table locked, and a second user is trying to establish a lock as well. This may be because of a FOR clause, but it is more likely because of pessimistic buffering or an explicit RLOCK() or FLOCK(). Have a look at the SET REPROCESS command. Here's the first part of the .HLP file from 5.0a: Syntax SET REPROCESS TO nAttempts [SECONDS] | TO AUTOMATIC Arguments TO nAttempts [SECONDS] Specifies the number of times Visual FoxPro attempts to lock a record or file after an initial unsuccessful attempt. The default value is 0, the maximum value is 32,000.