I am trying to fight a "Attempting to lock record...Press ESCAPE to canel" message I get on my multi-user app. When 2 or 3 people are adding and editing records to the system (which uses buffering on free tables), we get this message.

Set MultiLocks is ON.

I was wondering is the SET REPROCESS command might help.

Can anyone comment on the strategey and concept of this problem?

*******************************************************************************

How is your record / file locking being handled? If the files are being locked, you'll never free a user until the one who has the file locked turns loose of the file. Recommendation, use record locking. Big big huge, can't emphasize enough, when you lock a record (or file for that matter) turn loose of it as soon as at all possible. In a multi user environment, this is critical to performance.

One methodology that we use here is to use Views for the visibility of data. The views exist on the client side. A client DBC is created for the app on the user's local drive, and the views spin up from there. The only time the databases are locked is the instant during which the Fox engine writes updates made to their local view back to the original data. ** Note ** Any time you do an update, immediately issue a requery on the view to get the updates made by other users as well.

This is only one way, but it does alleviate the locking problem.

Regards,

Jason Tryon