RE: DSPFD to outfile has a Key Field Number field. QDBRTVFD api have similar ?

John,

I've also used QDBRTVFD with FILD0300, and as far as I know, the fields
are simply returned in order (you have to do your own counting).

HTH,

Peter Colpaert
iSeries Application Developer

Honda Europe NV
Langerbruggestraat 104
B-9000 GENT
Belgium
Peter.Colpaert@xxxxxxxxxxxx
Tel: +32 9 2501 334
Fax: +32 9 2501 231
----------
Yoda of Borg are we: Futile is resistance. Assimilate you, we will.
----------



"Rusling, John B. (Alliance)" <jbrusling@xxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
14/07/2004 15:49
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
<rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: DSPFD to outfile has a Key Field Number field. QDBRTVFD api have
similar ?






I've used DSPFD to an outfile in the past and it contains a field
indicating the order of the keys for a keyed file (Key Field Number).

I've setup the QDBRTVFD api to retrieve key field information,
using the FILD0300 Format.

I've perused thru the QDBRTVFD api (v5.2) and haven't been able to
figure where the order of the key fields comes into play/is returned.

I'm assuming one of 3 things...

a) I can't read what may be right under my nose

-OR-

b) the api returns the key fields in the proper key order.

-OR-

c) none of the above


If anyone can answer which of this (if any) is correct I would
certainly appreciate that.
(I don't care if it's answer a)  <g>

thanks for any help

John B.







The information contained in this communication is confidential and may be 
legally privileged. It is intended solely for the use of the individual or the 
entity to whom it is addressed and others authorised to receive it. If you have 
received it by mistake, please let the sender know by e-mail reply and delete 
it from your system.
If you are not the intended recipient you are hereby notified that any 
disclosure, copying, distribution or taking any action in reliance of the 
contents of this information is strictly prohibited and may be unlawful.
Honda Europe NV is neither liable for the proper and complete transmission of 
the information contained in this communication nor for any delay in its 
receipt.