[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | FOCUS, from INFORMATION BUILDERS |
|
Moderator: | ZAYIUS::BROUILLETTE |
|
Created: | Thu Feb 19 1987 |
Last Modified: | Mon May 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 615 |
Total number of notes: | 1779 |
108.0. "SET ALL=ON/OFF/PASS ?" by GVAADG::PERINO () Fri Aug 05 1988 13:29
We use the same relation in a recursive mode. We defined the relation
twice using an embedded join. It works usually fine but in some cases
when tring to report on fields contained in both relations we did not
obtain the same number of record than we had when reporting only on the
first relation. (see attached)
I solved it using SET ALL=ON but I do not really understand why it
worked because I could not find what was specific with the records
which were missing in the first request. I do not understand either
when I must set ALL to ON (or PASS). I am afraid that it changes the
results of other user requests.
Does somebody can give me more information than the one contained in
the FOCUS/Rdb booklet ?
Jo�l
DISCO.MAS
FILENAME=ALPHA ,SUFFIX=RDB,$
SEGNAME=ELEMENTS ,SEGTYPE=S0,PARENT=ENT_ELE,$
FIELD=ELE_ID ,ELEMENT_ID ,I5L, I4 ,MISSING=ON,TITLE='ELEMENT_ID',$
FIELD=ELE_PATH ,DIRECTORY ,A21 ,A21 ,MISSING=ON,TITLE='ELEMENT,DICTIONARY PATH',$
...
FIELD=B_ON_ELE_ID , ,I5L ,I4 ,MISSING=ON,TITLE='BASED-ON,ELEMENT_ID',$
FIELD=B_ON_ELE_PTH , ,A21 ,A21 ,MISSING=ON,TITLE='BASED-ON DICTIONARY PATH',$
SEGNAME=B_ON_ELE ,SEGTYPE=S0,PARENT=ELEMENTS,$
FIELD=B_ELE_ID ,ELEMENT_ID ,I5L, I4 ,MISSING=ON,TITLE='BASED_ON_ID',$
FIELD=B_ELE_PATH ,DIRECTORY ,A21 ,A21 ,MISSING=ON,TITLE='BASED_ON,DICTIONARY PATH',$
DISCO.ACX
SEGNAME=ELEMENTS ,TABLENAME=ELEMENT ,
KEYFLD=EE_ELE_ID/EE_ELE_PATH,IXFLD=ELE_ID/ELE_PATH ,$
...
SEGNAME=B_ON_ELE ,TABLENAME=ELEMENT ,
KEYFLD=B_ON_ELE_ID/B_ON_ELE_PTH,IXFLD=B_ELE_ID/B_ELE_PATH ,$
TABLE FILE DISCO
PRINT ELE_ID B_ELE_ID
The above request can give 33 records when the following gives 35
records.
TABLE FILE DISCO
PRINT ELE_ID
The 2 records do not contain a valid B_ON_ELE_ID but among the 33
listed records some do not either. ???
T.R | Title | User | Personal Name | Date | Lines
|
---|