×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The relative record number is already set to 10 and decrements by one for
each record read. I verified it dropping down during the debug process.
Have a good day.
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
1980 Ambassador Drive, PO Box 333, Windsor, Ontario N9C 3R4
Bus: 519-966-3003 ext. 566, Fax: 519-966-9870
blake.moorcroft@xxxxxxxxxx
jdavis@xxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/30/2009 01:50 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
cc
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>,
rpg400-l-bounces@xxxxxxxxxxxx
Subject
Re: Subfile reversing display
When you are loading the subfile for a previous page, you need to start at
RRN number 10 and work your way down to 1. Not 1 up to 10.
Jeff Davis
Blake.Moorcroft@xxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/30/2009 12:41 PM
Please respond to
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Subfile reversing display
Hello all...
I'm running into a really weird situation and I'm wondering if anyone's
ever encountered it before.
We're generating a subfile with 10 records (one page at a time, subfile
size and page = 10), nothing fancy, with both regular and hidden fields.
There are no issues with writing the records themselves.
When paging down (using the roll-up), the records proceed forward 10 at a
time in ascending sequence.
If, however, the page up key (roll down) is used, the records appear in a
reversed order - the correct records appear, just out of sequence. I've
included an example of what's happening:
Screen - starting position:
A Record
B Record
C Record
D Record
Screen after paging down:
E Record
F Record
G Record
H Record
Screen after paging up
D Record
C Record
B Record
A Record.
If we were now to hit the page down key again, we would get
E Record
F Record
G Record
H Record
The procedure is pulling the correct records, it's just not displaying
them in the proper way.
This subfile procedure is used in a number of programs. I use it any time
we need a subfile - basically cloned code. None of the other programs
that use this code are having the same issue - there are around 40
different programs using it. The logical that is used during the fill of
this particular subfile is not unusual - a three key index with ascending
controls on the keys - there are no omit or select functions. I have
checked the logical to verify the index properties.
I've checked the clear and display of the subfile and there are no
indicator issues.
I've stepped through the code with the debug procedure and watched how it
is writing the records, verifying the contents of each record's fields and
the relative record number associated to the record being written - there
are no issues and the relative record number is being properly assigned.
Any ideas?
Have a good day
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
1980 Ambassador Drive, PO Box 333, Windsor, Ontario N9C 3R4
Bus: 519-966-3003 ext. 566, Fax: 519-966-9870
blake.moorcroft@xxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Using an Expression to control a FOR loop, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.