Either a wait lock bias is specified for an operation but another user has locked the requested source, or the application is currently processing await transaction and tried to access a file that another user has locked. When you are using the Btrieve Requester to access Btrieve, the Requester waits and retries if a requested resource is locked. When a server-based application, such as NetWare SQL, is accessing Btrieve and the requested source is locked, a wait is also required. In this case, Btrieve would be expected to perform the wait. Since this would occupy Btrieve and lock out other users who might be trying to release the requested source, Btrieve does not perform the wait. Instead, it returns a status code 77, and the server-based application must retry later.
Back to index
Copyright © Madis Kaal 2000-