Kbase 9233: Results - .qc file structure: hacking, editing forms/joins
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Results - .qc file structure: hacking, editing forms/joins
910719-elp30
3.1 Manually Editing the Results .qc file
If you must edit the .qc file ouside of the admin module:
Back up the original .qc file first!
After that, the most important rule is:
Delete the fastload files (resxxxxx.r).
If you do not delete the fastload files, Results will rewrite the .qc
file, thowing away your changes and restoring the previous .qc file.
Reading the entire .qc file takes quite a long time.
Therefore, to speed things up, RESULTS creates res?????.r files which
contain ASSIGN statements to directly load up the shared variables.
As soon as the fastload line is reached, these programs are run, and
*everything from this point on in the .qc file is ignored*.
To restore the fastload files, simply go into Administration and then
leave it. RESULTS will re-write the .qc file, fixing any sequence
numbers and re-adding the fastload line. It will also rebuild the
res?????.r files to match the .qc file.
If the "checksum" is different, or the version does not match, the
fastload line is skipped and the entire .qc file is loaded. The V6
.qc uses a separate checksum value for each database on the
database#= lines.
3.2. Editing forms and joins.
If you edit the join#= lines, or (V5) view#= or (V6) form#= lines,
don't worry about messing up the numbering. RESULTS ignores the
numbers. The only *really* important thing is to keep the lists in
alphabetical order. But you can delete lines to your heart's
content.
3.3. Order of Options
Up to the "fastload" line, *do not change the order of options*!
This is very important! However, after the fastload line, it doesn't
matter whether forms come before views, or permissions, or printers.
As long as each group is together. Going in to Administration and
leaving will re-write the .qc in a form that makes RESULTS happy, so
again don't worry too much.
3.4. "view#=" and "form#="
In V5, query form lines begin "view#=". This has been changed to
"form#=" in V6. Note that V6 will still read "view#=" properly for
the near future.
3.5. Join Changes in V6
In V5 RESULTS, we stored each join twice - once "x to y", and again,
"y to x". In V6, we support what we call "symmetric joins" - that
is, if you can join "x to y", this implies that "y to x" also works.
In V5 RESULTS, you could delete half a join - you could remove "y to
x", leaving "x to y" available. With V6 symmetric joins, you cannot
do this. Half joins are converted to symmetric joins in V6.
RESULTS will automatically convert your join list when you switch
from V5 to V6. We always store the name that comes first
alphabetically as the first name of the join pair. For example, you
will see "customer to order" in the join list, but never "order to
customer". But remember that in V6 "customer to order" implies
"order to customer".
Progress Software Technical Support Note # 9233