Kbase P17788: Getting error 138 when starting Results
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2003 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT
FACT(s) (Environment):
Progress 8.3C
FACT(s) (Environment):
Results
SYMPTOM(s):
Getting error 138 when starting Results:
** qbf-join record not on file. (138)
** <qbf-section> record not on file. (138)
CAUSE:
The error qbf-join record not found (138) can come when a .qc7 or FastLoad rcode is lying around from a previous build; or when the wrong qc7 file is being found.
The QC7 file (query configuration file) contains information about table relationships (e.g. joins), security, export formats, label formats, page formats, etc. for a Results application. When you start Results with a database or set of databases for the first time, Results builds a QC7 file and names the file using the name of the first database connected (dbname.qc7).
FIX:
Check the location of the qc7 file required and ensure that the correct qc7 file will be found by Results.
By default, Results tries to create the QC7 file in the same directory that contains the first database connected. However, if the database is on another machine, Results might not be able to reach that directory. In that case, Results places the QC7 file in the current directory. Once Results creates the QC7 file, you can move it to any directory in the PROPATH. When you start Results, it first searches the current directory and then the directories of the PROPATH for a QC7 file.