RE: Ad Hoc key list error

Tony,
Are you saying that LIKEREC(myFile : *KEY) doesn't give you just the key
fields in the order they appear for that file?  It is supposed to be doing
that.

-Bob Cozzi
www.RPGxTools.com
If everything is under control, you are going too slow.
- Mario Andretti


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Tony Carolla
Sent: Tuesday, May 03, 2005 10:20 AM
To: RPG programming on the AS400 / iSeries
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.