RE: Secondary Keys

[D.BALE@xxxxxxxxxxxxx]

I think you may want to take another look at that.  I may not have understood
your objection to JDUPSEQ, but even if the user is able to specify a "Position
To:" on a secondary file field, you would still be able to SETLL with those
key fields that are in the primary and then use READE until you find the key
value on the secondary file field.  It really depends on how many dead READE's
you'd have until you find the record you're looking for.  And that depends on
how far down your key list the first occurrence of a secondary file field is
found.

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

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

Stan,

Thanks, but I do have a 'Position To:' function built into my sort
selection. It positions based on the values keyed in by the user. If I read
to the position based on the values keyed, I have the same problem as
building a work file except the problem occurs when positioning during the
application instead of once at the beginning: The delay will take too long.
So, I don't think JDUPSEQ is going to do it for me.

Patrick Conner
www.ConnecTown.com
(828) 244-0822
+---
| 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
+---