Record stuck in Pervasive with no KID (Key ID=0)
Record stuck in Pervasive with no KID (Key ID=0)
KID is zero which should never happen. Will always happen to the LEAD pax.
So if you have a lead pax that shows up in every report for trips they are not even on, more than likely these instructions below will fix the issue.
There are 5 KIDs created:
1. Date
2. Time
3. User
4. Mult
5. Comm
When record is created a unique KID is created.
With FOS open on the server, go to Start – Pervasive – Control Center. Expand the computer name – databases- FOS data – Tables
Go to the Trip Passenger Table
Type in this:
With cursor in the space below, right click and choose Execute in Grid
In the bottom there should be a record for the name that was populating, right click and delete row
Once done, exit out and chose NO on the message
Related Articles
Changing an Aircraft ID
If you need to change an Aircraft Record's ID there are specific steps that need to be follow to make sure you successfully maintain the record's historical data. 1. Make sure all other users are out of FOS 2. Open the Aircraft Database and then the ...
Extracting Data from FOS Pervasive Tables
Installing Pervasive & Initial Information *If Pervasive is already installed on the machine, please skip to the next section (Extracting Data from the Pervasive Database)* Before beginning the extraction, you will need to download and install ...
Error: Invalid regulation key
Error: ----Online Subpart Q Legality Checks Run---- Invalid regulation key ----Online Subpart Q Legality Checks End---- Solution: This error displays all other positions on the trip, aside from PIC. This error may occur if the FM credentials are ...
Error: Pervasive Database is already in use
Error: Pervasive Database is already in use. Solution: If the FOS Database is not listed in the Pervasive Control Center, however the user receives an error that the database already exists when trying to create the database open the registry editor. ...
Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1)
Error: Requested key not found (error=4) sch_data_read_ac_single: aircraft_get (Thread 1) Solution: An Aircraft Record was deleted from FOS or changed incorrectly. The record will need to be added back to FOS with the same tail and AC ID.