RE: Secondary Keys

Bored?  Who, us???  I laughed when I read your "must be bored" message, the
first of about ten emails sitting in my inbox with the subject "Secondary
Keys". <g>

Thanks for the additional info.  However, I am confused about two statements
which seem to be in conflict with each other:
   >I created a matching join logical with File2 as the primary
   >file. This way if there are any records in File2 not matching
   >File1 they will not show up in the subfile.
vs.
   >Now the problem. If a record is added to File1 that does not
   >have a matching key in File2, I can't see it in my subfile.

Does it matter that it was just added?  If you don't have a matching key, did
you still want to see it in the subfile?  If you do, perhaps you shouldn't be
matching the particular field that's not matching.

Bored?  We're just cutting to the chase!

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------

Good observation. This is where I started. Currently the program only has
two sorts. These use fields solely in the primary file, File1. No problem.
No join. I chain the secondary file, File2, for subfile info. Now, the
request for the third sort. All fields are in File2. I created a matching
join logical with File2 as the primary file. This way if there are any
records in File2 not matching File1 they will not show up in the subfile.
Now the problem. If a record is added to File1 that does not have a
matching key in File2, I can't see it in my subfile. Hence, I need File1 as
the primary file joined with default values to File2.

I had no idea this topic would get this much attention. And I was worried
about boring you folks.

Patrick Conner
www.ConnecTown.com
(828) 244-0822


Chris Bipes said:


Are all the Key fields in one file for the sort in question?  Are you
trying
to sort by multiple fields at the same time?  IF you are only sorting on
fields in one file at a time, though the user can select to sort by A or B
or C and they could be in different files is to create the join with the
secondary file first.  What I mean is to reverse the order of the join in
creating the LF.  That is if the data will allow it.  I don't know your
data
bases therefore can only guess if it is possible.

Now if you are joining file1 to file2 on field a but need it sorted by
b/c/d
and b & c are only in one file with d in the other.  Create the LF with the
keys B & C.  Then use OPNQRYF with a sort by B & C & D, but force a record
selection such as for product group A only.  That is how we went about it.
Queries can take 10 - 30 seconds depending on how many records meet the
selection criteria.


Christopher K. Bipes           mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst         mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.               http://www.cross-check.com
6119 State Farm Drive          Phone: 707 586-0551 x 1102
Rohnert Park CA  94928         Fax: 707 586-1884
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---