Kbase P117913: What are the QUERY/RESULTS generated files?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/1/2009 |
|
Status: Verified
GOAL:
What are the QUERY/RESULTS generated files?
GOAL:
Where are the QUERY/RESULTS files?
GOAL:
How to move the QUERY/RESULTS files?
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
GUI RESULTS:
database.qc7: The query configuration file (QC7). The query configuration file contains the default file relationships, security settings, label settings, data export settings, and report settings for a Results application. The database value is the name of the first application database connected for the Results application. Results cannot run without the QC7 file. For more information about query configuration files, see Chapter 2, "Administering Results."This appendix provides information about editing a QC7 file.
database.r: The main fastload procedure for a Results application. The fastload system optimizes the loading of information from the current QC7 file into Results at startup. The database value is the base string specified in the Deployment dialog box for the generation of fastload files for a Results application. The default base string is the first five characters of the database name used to name the current QC7 file. For more information about the fastload system for a Results application, see Chapter 3, "Programming Results."
base###.r & baser.r: Secondary fastload files. Base is the base string specified in the Deployment dialog box for the generation of fastload files for a Results application. The default base string is the first five characters of the database name used to name the current QC7 file.
basef.p & basef.r: The feature files of a Results application. The feature file is a Progress procedure file in the fastload system that defines and loads features into Results at startup. The basef.r file is not a compiled version of the basef.p file. It is optimized for fast loads and accesses internal data structures of the Results product. The source code in the basef.p file performs that same function as the basef.r file, only slower. It is supplied to support the deployment process of a Results application. For more information about the fastload system for a Results application, see Chapter 3, "Programming Results."
basemt.p & basemt.r: The user interface (UI) files of a Results application. The UI file is a Progress procedure file in the fastload system that configures the menu system and tool bar of Results at startup. The basemt.r is not a compiled version of the basemt.p file. It is optimized for fast loads and accesses internal data structures of the Results product. The source code in the basemt.p file performs that same function as the basemt.r file, only slower. It is supplied to support the deployment process of a Results application. For more information about the fastload system for a Results application, see Chapter 3, "Programming Results."
public.qd, userid.qd7 & results.qd7: Query directory files. The public query directory (public.qd7) contains query definitions accessible by all or a select group of users. Results also automatically generates a query directory to store the query definitions of a user (userid.qd7). It uses the user's user ID to name the query directory file. For users who have the blank user ID, Results creates the results.qd7 query directory file to store the query definitions of that user.
que#####.p: Source files for query definitions in the query definitions files located in the current directory. Results creates query source files in the directory that contains the corresponding query definition. Query source files are five-digit numbers (#####). Results uses these numbers to maintain the queries. If you delete a query source file, you cannot open the corresponding query in Results.
database.ql: A query log file. Results uses this file to record status and error messages that occur when you build the query configuration file or open a query. For more information about the query log file, see Chapter 2, "Admin.istering Results."
base.txt: The deployment report for a Results application. This file lists the files to deploy for a Results application. Base is the base string specified in the Deployment dialog box for the generation of fastload files for a Results application. For more information about the deployment report, see Chapter 4, "Deploying Results Applications."
_qbf####.d, _qbfq####.p, _qbf####.p & temp.p: Temporary files that Results uses to store information. As you exit Results, it automatically deletes these files. But if your system crashes, they could remain on your disk. You can delete them manually.
The query configuration file database.qc7 may be moved to any directory which is in the PROPATH. The fastload, feature file, may be moved to any directory provided that the query configuration file database.qc7 is edited to indicate their locations. The query configuration file database.qc7 may be edited (Back it up first!). In this case, delete the fastload files before you run Results otherwise, RESULTS will ignore the changes you made in the .qc7 file because it is will be using the compiled fastload files instead. For example, to move the feature-files basef.p & basef.r:
1. Edit the query configuration file database.qc7 file and modify line that begins "feature-file=" to point to the new directory of the feature-file.
2. Delete the fastload files: database.r, base###.r and baser.r.
3. Move the feature-files: basef.p & basef.r to their new location.
To move the fastload files moved to a different directory:
1. Edit the query configuration file database.qc7 file and modify line that begins "fastload=" to point to the new directory of the feature-file.
2. Delete the fastload files: database.r, base###.r and baser.r.
1. Edit the query configuration file database.qc7 file and modify line that begins "fastload=" to point to the new directory of the feature-file.
2. Delete the fastload files: database.r, base###.r and baser.r.
3. Results will create new fastload files in the new location before you exit your Results session.
Alternatively, the location of these files may be controled from within Results as follows:
Choose Query -> Customize -> Deployment.
Any changes made here will be written to the .qc7 file when exiting Results. You may also rename these files here. After making changes here, it is safe to delete the old files from your system.
In addition to the above files, the file named results.l is in the directory directory dlc/gui/aderes. This file contains all of the possible languages that can be used with Results and sets the current language. The default is "eng" or English. This file also contains the default values for export, label, and page size.
CHARACTER RESULTS (TTY):
.qc file: The query configuration file (QC). The .qc file is the configuration file that contains the list of permissions, printers, joins, etc. By default, Results tries to create the .qc file in the same directory that contains the database (dbname.db). However, if the database is on another machine, Results might not be able to reach that directory. In that case, Results places the .qc file in the current directory.
resxxxxx.r: TTY RESULTS fastload files.
.ql file: The query log file. (QL). The .ql file is the query log file. During the initial system generation, this file logs the files that have query interfaces built for them, as well as any problems encountered during the build. Results creates it in the same directory that contains the .qc file.
.qd file: The query directory file (QD). The .qd file is the query directory file. The name of the .qd file is the first eight characters of the USERID plus the .qd extension. If the USERID is blank then the name is results.qd. Results takes the USERID from LDBNAME(1), which is the first connected database. The .qd file contains the directory that maps the descriptions of reports, labels, and export programs to their filenames.
repxxxxx.p, lblxxxxx.p & expxxxxx.p files: The user report, label and data export files. Each user has their own reports, labels, and export files. The filenames have the format repxxxxx.p, lblxxxxx.p, and expxxxxx.p, where xxxxx represents a unique integer value.
qbf*.p & qbf*.d Files: These are temporary files (_qbf*.p and _qbf*.d) created by the RESULTS session. These files are placed in the current directory. If several users share that same directory, these files will overwrite each other.
The query configuration file .qc may be moved to any directory which is in the PROPATH provided that the query log file .ql is also moved to the same directory.
In TTY RESULTS, the path of the fastload files is not hard-coded in the .qc file. Therefore, the fastload files may be moved to any directory as long as that directory is in the PROPATH provided that the query directory file (QD) and the report files are in the same directory.
If you make changes in the Administration module, Results will prompt you to do an application rebuild. Updates will be made to the fastload files and they will be saved to the same directory the fastload files were found in. However, if you create new query forms, the new query form files will continue to be saved to your working directory. After they are created, you may move them to any directory in your PROPATH. There is no feature-file in TTY RESULTS.
In addition to the above files, the file named results.l is in the directory directory dlc/tty/aderes. This file contains all of the possible languages that can be used with Results and sets the current language. The default is "eng" or English. This file also contains the default values for export, label, and page size.
If RESULTS is unable to write its files to the database directory, it will write them to the user's working directory..