Btrieve Error: (Btrieve Error 8020). Cannot name the componentTAble name is Flt Leg. Component is FltLegTable, owned by InterfaceForm.

Error: 

(Btrieve Error 8020). Cannot name the componentTAble name is Flt Leg. Component is FltLegTable, owned by InterfaceForm. 

 

Solution: 

This error occurs with Pervasive 10 and lower. The DRM.DLL file will need to be removed from the FOS Folder, on the FOS Server.  

• Related Articles

• Btrieve Error: (Btrieve Error 35). Table name is FLT Leg. Component is FltLeg Table, owned by InterfaceForm

  Error: (Btrieve Error 35). Table name is Flt Leg. Component is FltLegTable, owned by InterfaceForm. Support Solution: When accessing the Flight Data Table and Btrieve Error 35 is displayed, please follow steps below. 1. On the FOS Server, open the ...

• Btrieve Error: Btrieve error 8020 access_refresh_company: compinfo_open (Thread 0)

  Error: Btrieve error 8020 access_refresh_company: compinfo_open (Thread 0) Btrieve error 8020 FOS can not open the Btrieve data files. Use the Utilities | File Locations drop down menu to set the Data and Temporary Directories. password_init: ...

• Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0)

  Error: Btrieve Error: I/O error during disk read/write (error=2) audtrail: btrieve_status(Thread10428) (Thread 0) Solution: Error message is received upon login to FOS for all users. Clear all Pervasive Sessions and/or reboot the FOS server.

• Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)

  Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0) Solution: Btrieve error 3006 generally means the client machine and FOS server are not communicating. It is possible that there are hung sessions in Pervasive which may be ...

• Btrieve Error: Btrieve Status 2 - The Application encountered an I/O error DBIERR_READER

  Error: Btrieve Status 2 - The Application encountered an I/O error Key = [chklist.btr] DBIERR_READER Solution: If only a few users are seeing this error message and the users are on Pervasive version 12, the Collins Engineering Team can try ...