Hi. I am working on an old Fox DOS 2.6 app in a multi-user environment.

When I select Read NoLock in my compile options, the screen becomes read only. The cursor is visible
in a field and beeps when a key is pressed and no character enters.
When Read NoLock is not checked, the second user gets an "attempting to lock" message.

This has not been a problem in the past, only recently. I have multilocks on and reprocess to automatic.

Thanks, Randy