In the documentation that I have there is a description of 85 as below - hope it's of some help:
85: The file is locked.
The MicroKernel returns this status code in one of the following situations:
* The workstation MicroKernel has a file open, and another workstation that has the Requester loaded tries to open the same file via the server MicroKernel. The server MicroKernel cannot open the file since it cannot obtain exclusive access. The workstation that has the Requester loaded receives this status code.
* In a workstation engine environment, the MicroKernel can return this status code on an Open, Insert, Update, or Delete operation for a file under heavy usage by multiple users or tasks. The MicroKernel must momentarily have exclusive access to the file during these operations, and it retries the operation several times before returning this status code. In this case, the application can reissue the operation. In addition, you can reconfigure the workstation MicroKernel with a lower Operation Bundle Limit and Initiation Time Limit to reduce the amount of time the MicroKernel keeps a lock on the file. Refer to the User's Guide for more information about how to do this.
* In a workstation environment, a v6.15 or later MicroKernel has a pending modification (insert, update, or delete) as an incomplete system transaction in a file that has been opened in MEFS mode. If multiple users or tasks attempt to access (Get/Step) or modify (insert, update, or delete) the shared file, the MicroKernel returns this status code. An access operation can receive this status code only if the writing phase of the system transaction has started.
Reconfiguring the MicroKernel with a lower Operation Bundle Limit and Initiation Time Limit reduces the occurrences of file contention that produce this status code. Refer to the User’s Guide for more information about how to do this.
If you are a developer and want more information about system transactions, refer to the Programmer’s Guide.
* While one user has a file locked in an exclusive transaction, another user attempts to lock all or part of that file.
* When opened by a server MicroKernel, a file is in transition into continuous operation mode. Retrying eventually works.
* When opened by a server MicroKernel, two data files have the same filename but different extensions (for example, INVOICE.HDR and INVOICE.DET). One file is open and in continuous operation mode, causing the MicroKernel to generate a delta file (for example, INVOICE.^^^). The MicroKernel returns this status code when you attempt to open the second file.
* When opened by a Windows NT server MicroKernel using Microsoft File and Print Services for NetWare on behalf of a 16-bit Windows workstation, the file was also opened simultaneously by a 32-bit Windows NT or Windows 95 workstation. Doing so causes the server MicroKernel to open the same physical file using two different paths.