Kbase 16331: Effects of index changes to Results reports and OF joins
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Effects of index changes to Results reports and OF joins
How does Results create "OF" joins during the initial build of the .qc
file? Results looks for the primary key of each table. It then
searches for a field in another table which has the same name and
datatype. It does not matter if this "foreign key" field has an index
on it. If a match is found, Results creates an "OF" join between the
two tables and stores this information in the .qc file (or .qc7 file
if in GUI Results).
If someone makes a change to the index of a table in the database,
Results detects that a change has been made when you bring up Results.
You are promted to do an application rebuild. If someone has changed
the primary key of a table, this will effect what "OF" joins are
created and stored in the .qc file. Reports that previously had
depended on a join which now no longer exists will no longer run.
Attempts to run these reports will result in a series of error
messages. The reports still exist and have not been changed, they
just can no longer be run without the proper joins in place. You may
restore the needed joins by going into the Administration module.
Under FILES, choose Relations Between Files and create the needed
join. (In GUI Results, choose Query -> Site Admin -> Table
Relationships.) When you leave the Administration module, the changes
you have made are written to the .qc file and the FastLoad files.
(In GUI Results, this happens when you exit Results).
Progress Software Technical Support Note # 16331