Thanks for the FORMAT and INDEX hint. I gues the ON TABLE HOLD INDEX KEY_FIELD1 is also needed for TABLE FILE F1 if I want to use it in the following JOIN?
I did a COMPUTE in the first HOLD. The problem now is that WebFocus does not know this field when I create a TABLE after the JOIN with PRINT COMPUTED_FIELD. Does that mean that computed fields are not onsidered in the join? Do I have to make a DEFINE after the Join instead?
Indexing join key in the master table (H1 in the example) is not necessary, but not harmful as well.
COMPUTEed fields in the HOLDed files are just the normal fields.
Could you send a sample code ?
You can also put
Code:
-SET &ECHO=ALL;
in the first line of the focexec, the generated report should contain some useful information within HTML comments.
Actually, you can JOIN two HOLD files, but there are certain rules and restrictions. These are a result of HOW we do the JOIN with sequential files. We NEVER back up. As a result, the 2 rules are:
1. Both files must be sorted in ascending order, on the common field (used for the JOIN).
2. There can be duplicate values in only ONE of the files. If in the host, the you should use a JOIN ... TO ...; if in the target use JOIN ... TO ALL .... If there are duplicates in both files (which would require us to back up to correctly process, then use the HOLD FORMAT FOCUS INDEX syntax on the target file, so the above rules no longer apply.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.