Re: Ad Hoc key list error

["Richard ECUYER" <recuyer@xxxxxxx>]

what i always do is prefix the key field :

My file :
field1, field2 ...
The key :
k_myfile            klist
                         kfld                k_field1
                         kfld                k_field2

with this, i have more lines to populate the key fileds, but i can't use a
field from another file or another ds...
----- Original Message ----- 
From: "Tony Carolla" <carolla@xxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, May 03, 2005 5:19 PM
Subject: Re: Ad Hoc key list error


Good Morning!

<snip>
On 5/3/05, Reeve <rfritchman@xxxxxxxxx> wrote:
>
> Unless there's a reason to do otherwise (such as changing the key), I
> always use the file's key field name(s) in any key field specification
> (in both fixed and ad-hoc formats). This eliminates problems like
> this but, more importantly, it documents the acess logic. It's
> another line of code but it's nice having it there; debugging becomes
> a lot easier.
>
> -reeve

</snip>


I agree totally, but it doesn't always elim the problems. I was using the
fields from a DS that was built using LIKEREC against the record format of
the file itself. The problem was that all keys were numeric, and different
lengths,,, and they were in the wrong order on the key spec.



-- 
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought
-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.