Inconsistent File Name in Btrieve Error Window

Inconsistent File Name in Btrieve Error Window

Release Date: 09/11/20
Version: 7.x - 8.5

Q - I notice that sometimes in a Btrieve Error window, the physical file and the file name are not consistent.  Take, for example, the following error message:
    EL850P: Btrieve Error 067 on NSCTLFIL COP Control File

NSCTLFIL is the NS Control File, not the COP Control File. Why the inconsistency?

A - This may happen if there is an error in a non-Btrieve file. In this case, the COP Control File is CPCTLFIL.DAT, which is not a Btrieve file.  The DAT file is handled by the Run time and does not go through the Elliott Btrieve file handler. So when there's an error, we have the "COP Control File" information. But we don't have the physical file name. 

In this case, the error is in a COP Control File, and the system manager assumes the last file system access in the Btrieve File Handler is the one that caused the error, which is NSCTlFIL in his case. NSCTLFIL.BTR actually does not have an error, so this is misleading information.  This issue will be addressed when Elliott converts all DAT files to BTR in the future version of Elliott.

This inconsistent file name issue is no longer a problem with Elliott V8.6 and up.

EMK


    • Related Articles

    • Btrieve Error Codes 001 - 199

      MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. That is ...

    • Inconsistent Elliott Error on Terminal Server

      Q - We occasionally run into an issue with our terminal server where Elliott crashes after entering the username/password. After clicking on the shortcut, it prompts for the username / password. After clicking OK, it crashes. We are confused because ...

    • Btrieve Error Codes 3000 - 3099

      MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel ...

    • Btrieve Error Codes 3100 - 3199

      Network Services Layer Status Codes The following status codes originate from the Pervasive Network Services Layer (PNSL). 3103: Server name not found by Pervasive Network Services Layer The search for a target server name was unable to resolve an ...

    • Btrieve Error 025 on COP Open Order by Salesman Report

      Q - When I run COP -> Reports -> Open Order by Salesman Report, I receive Btrieve Error 025. What causes this error? See sample screen below: A - Typically this is caused by a work file usage conflict. This means another user is in the middle of ...