FMSweb5 Welcome myacct


Untitled Document CLS Frequently Asked Questions

B. Common Btrieve Errors

1. Btrieve error - Disk I/O error
This error can occur because CLS detects a real disk I/O error (where the operating system can no longer read a particular sector on the disk). It can also occur when CLS is using Btrieve 5.10 to try to open a data file created in the Btrieve 6.xx file format.

Btrieve, by Pervasive Software, is the file manager used by CLS. It runs in the background, reading and writing the indexed files used by CLS. The Single-User version of CLS ships with Btrieve 5.10. The Network version of CLS uses Btrieve 6.15, which has been configured to be compatible with Btrieve 5.10.

Normally, CLS data files are interchangeable and can be read by all versions of CLS. However, under some circumstances CLS data files may be converted to the Btrieve 6.15 format:

  • If the data files were originally stored on a Novell Netware 3.xx or 4.xx server, and CLS was using the server version of Btrieve 6.15 supplied by Novell.
  • Several years a few CLS users were mailed a diskette containing a copy of Btrieve 6.15; this version was not set up for Btrieve 5.xx compatibility.

If you believe that your CLS data files might have been created with Btrieve 6.xx, it’s easy to check the version of Btrieve used by your current version of CLS:

  • Start CLS and go to the main CLS menu. At the Which program would you like to select? prompt, type DS and press Enter. At the DOS (Command) prompt, type dir btrieve.exe and press Enter. If the file size is 43,036, CLS is currently using Btrieve 5.10; if it is 309,725, it’s using Btrieve 6.15. Type Exit and press Enter to return to CLS.

The CLS 5.41 CD-ROM contains a copy of both versions of Btrieve. If you’re currently using Btrieve 5.10, and would rather use Btrieve 6.15, please call CLS Technical Support for help with the installation.

Top of Page
Return to CLS FAQ's Home


2. Btrieve error – Btrieve not loaded
This error can have several possible causes:

  • If CLS is already running and you attempt to start it a second time, you may see this error. If it occurs, simply close both copies of CLS and start over. Occasionally, you may also need to reboot your workstation.
  • When adding a new CLS icon to your desktop, be sure to use CL.BAT as the command to start CLS. CL.BAT first loads Btrieve into memory and then runs CLS. If, instead, you use CLSTART.EXE to start CLS, Btrieve will not be loaded into memory, and CLS cannot function properly.
  • This error can also occur on a workstation running Windows 98 if you install a Windows-based software package that uses Pervasive SQL 2000 (based on Btrieve). When SQL 2000 is installed in this environment, support for the version of Btrieve used by CLS is automatically disabled and CLS will not run. If you think you may have this problem, use Windows Explorer to search your workstation for the PVSW directory.

    If you find it, call CLS technical support for help restoring access to the CLS version of Btrieve. (There is no charge for this service).

Top of Page
Return to CLS FAQ's Home


3. Btrieve error - File locked
Normally, this indicates that a ledger file that CLS is attempting to open is already in use. Verify that CLS is not already running on your workstation (it may be minimized). If this is not the case, you will need to reboot your workstation.

In some cases, it can also indicate that a data file is really locked. If this is the case, and the CLS data is located on a server, you will also need to reboot your server.

Top of Page
Return to CLS FAQ's Home


4. Btrieve error 30
This error can occur if you install a Windows-based software package using Pervasive SQL 2000 or SQL V8 (both of which are based on Btrieve) on a workstation running Windows 2000 or XP. In this case, the version of Btrieve supplied with CLS is automatically (and silently) replaced by the newer version provided with Pervasive SQL.

As CLS ledgers are worked on with this new version of Btrieve, some CLS data files may be converted to the Btrieve 7 (SQL 2000) or Btrieve 8 (SQL V8) file format. If you then try to access these ledgers from a workstation that is not running SQL 2000 or SQL V8, you will see this error.

When solving this problem, there are really two issues to deal with:

  • The affected CLS ledgers need to be converted back to a CLS-compatible file format (Btrieve 5.xx or Btrieve 6.xx), so that they can be accessed by any workstation running CLS.
  • You may wish to restore access to the version of Btrieve supplied with CLS. However, this step should not be taken until all of the accidentally converted ledgers have been converted back to a CLS-compatible format.

If you think you may have this problem, use Windows Explorer to search your workstation for the PVSW directory. If you find it, please call CLS technical support for help

Top of Page
Return to CLS FAQ's Home


5. Btrieve error 42
Indicates that a Btrieve file was opened in the “accelerated” mode and not closed properly (i.e., you did not exit CLS normally). This type of error is more likely to occur if ledger data files are stored on a floppy disk, or if you were working in the CLS Bank Reconciliation program. (It can also happen at other times, but it’s not very likely.)

Normally, Btrieve will repair CLS data files automatically. However, if a data file was opened in the accelerated mode, automatic recovery is not possible. To correct this error, run VF 3, Force Recovery of Master Files.

Top of Page
Return to CLS FAQ's Home


6. Btrieve error 88
A Btrieve error 88 occurs when CLS tries to open a non-shareable file that is already in use by another process. It normally occurs when one of the temporary files used by CLS is accidentally left open.

If you are using the network version of CLS, the server (and all workstations) must be shut down and rebooted.

If you’re using the single-user version of CLS, try rebooting the workstation first. If that doesn’t solve the problem and your CLS data is stored on a server, then you will need to reboot the server as well.

Top of Page
Return to CLS FAQ's Home


Contact Us |  Support |  Privacy Policy |  Site Map
Copyright 2017 - Financial MicroSystems, Inc. All rights reserved.