RE: Accessing a File with a Variable Key

What's the problem?

I know of no reason why a file variable key field would need to be treated any
differently than one
with a fixed key field in RPG IV. I must admit that I've never tried it though
;-)

You don't by chance have CVTOPT(*VARCHAR) specified in an h-spec or on the
CRTBNDRPG/CRTRPGMOD
commands do you?

If so, take CVTOPT out. It's really only there for RPG III programs that are
run through CVTRPGSRC.
Native RPG IV programs handle variable length fields just fine.

Charles

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Fred Horvat
Sent: Thursday, June 07, 2007 3:39 PM
To: RPG400-L@xxxxxxxxxxxx
Subject: Accessing a File with a Variable Key

How does one go about accessing file that one of the key
fields is a variable length field in ILE RPG? I have to add
such a file to an existing program. Only thing I could think
of was with Embedded SQL. Is there any other way or is
Embedded SQL the only way?





Fred Horvat

horvat@xxxxxxxx

216-426-5692



--
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.

This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a
named addressee you are hereby notified that you are not authorized to read,
print, retain, copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be unlawful. Please reply
to the message immediately by informing the sender that the message was
misdirected. After replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in correcting this
error is appreciated.