DB Error 100 in Infor LN and Baan: Record or End of Set Not Found

How to trace and fix db error 100

1. 1Note the exact session, the table (shown in the error text) and the action the user took when the error appeared.
2. 2Reproduce it with the same data. If it only occurs for one record, the key values are the clue: a missing master record, a mismatched key, or a deleted row.
3. 3Run the session under the Application Debugger or with the debug option and break where the database operation is called. Inspect the key fields of the table record before the call.
4. 4Check the return value of the operation with the db error function right after the call, and confirm that the number is the not-found code in your porting set error list.
5. 5Look for a missing reference: a child record points to a parent that was archived, deleted or never existed in this company (cross-company data is a common reason).
6. 6Look for a wrong index: the code searches on one index but the key fields are filled for another.
7. 7Fix the data if the record should exist, or fix the script to test for the not-found condition and branch instead of continuing with an empty record.
8. 8Recompile in Studio and retest with the same record and with a record that does exist.

Handling it in 3GL code

select tccom001.*
from   tccom001
where  tccom001._index1 = {:cuno}
selectdo
    process.record()
selectempty
    mess("customer.not.found", 1, cuno)
selecterror
    abort.transaction()
endselect

Common pitfalls

• !Using the record buffer after a not-found read, which still holds stale values from the previous record.
• !Treating every non-zero db.error as the same and hiding real errors behind a not-found branch.
• !Searching with the wrong index for the key fields that were filled.
• !Testing only with a record that exists, so the not-found path is never exercised.
• !Fixing the symptom in the script when orphaned data is the real problem.