Kbase 16405: Results files - what, where, can I move them?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Results files - what, where, can I move them?
Results files: where are they - can I move them?
In Gui Results, query files are called que#####.p. A list
of your reports is saved in a query directory file called Results.qd7
(or <UserId>.qd7 if security is enabled). These files are saved
to your working directory. The query files and query directory must
always be located in the same directory. There are also several
temporary files (qbf.p, qbf.d, etc.) that Results creates in the
working directory as needed.
All other files Results generates are saved to the same
directory the database is in. These include the .qc7 file,
the fastload files (these are named the first five letters of
the first database you are connected to, plus "s" or "r" or "00#",
plus .r), the feature file (first five letters of the database,
plus "f", plus .p or .r), the menu-and-toolbar file (first five
letters of the database, plus "mt", plus .p or .r), and the
deployed application file list (first five letters of the database,
plus .txt). For detailed information on files generated by
Results, see appendix C of the v8 Results Administration and
Deployment Guide.
You may move the .qc7 file to your working directory. You
may also move the .qc7 file to any directory which is in
your PROPATH.
You may move the fastload, feature file, or menu-and-toolbar files
to any directory you choose, but you must tell Results where
to find them. The path to these files is defined in the
.qc7 file. You may edit the .qc7 file (making sure to
create a backup first!) provided you delete the fastload
files before you run Results. If you do not delete the
fastload files first you will get errors such as:
"There is a problem with C:\work\sportf.p. Results will
continue with its default feature set"
"Sportmt.p not found"
"There is a problem with c:\workdir\sportmt.p. Results
default menu and toolbar will be used".
(Results is ignoring the changes you made in the .qc7 file
because it is using the compiled fastload files instead.)
For example, if you want to move your feature-file:
(1)Edit the .qc7 file. Change the line which begins feature-file=
and fill in the path of the new location for the feature-file.
(2)Delete the fastload file.
(3)Move the feature-file to its new location.
If you want the fastload files moved to a different directory:
(1)Edit the .qc7 file. Change the line which begins fastload=
and fill in the path where you want Results to save the new
fastload files.
(2)Delete the existing fastload files. Results will create
new fastload files in the new location before you exit your
Results session.
As an alternative to the above, you may control where Results
will create the fastload files, feature files, and UI files (menu
and toolbar) from within Results. 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 the directory dlc/gui/aderes, there is a file called results.l
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.
=====================================================================
In tty Results, the behavior is different.
Report files are called rep#####.p. A list of your reports
is saved in a file called <UserId>.qd. There are four files
created for each query form. These are named after the file
associated with the query form. For example, a query form for a file
called customer would produce customer.p, customer.f, customer.r, and
customer.i. There are also several fastload files. These are called
res#####.r. These files are all saved to your working directory.
(remember in GUI, fastloads are saved to your database directory).
The working directory is the directory you are in when you start
Results. All other files are saved to the same directory
where the database is located.
You may move the .qc file to your working directory. You
may also move the .qc file to any directory which is in
your PROPATH. However, if you move the .qc file, you must also
move the .ql (query log) file to the same directory.
In tty Results, the path to your fastload files is not
hard-coded in the .qc file. Therefore, you are free to
move the fastload file from the database directory to your
working directory without editting the .qc file. Results
will look for the fastload files in your working directory
if it does not find them in your database directory. You
are also free to move any file to any directory as long as
that directory is in your PROPATH. However, you must keep
the .qd file and the report files together 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 or menu-and-toolbar file
in tty Results.
In the directory dlc/tty/prores, there is a file called results.l
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.
Note: if Results is unable to write files to the directory
where your database is located (as in the case where you
have a windows client and a Unix database), Results will
write files intended for this directory to your working
directory instead.
Progress Software Technical Support Note # 16405