RE: Single Page/Expanding/Load all subfile USAGE

["Booth Martin" <booth@xxxxxxxxxxxx>]

I like all of these suggestions but offer one more.  Instead of a multi
occurrence data structure, just define a data structure with the external
name of the file, then load the data structure as a hidden field on the
subfile record.  Another advantage of this technique is that you have a true
before-image to use for a compare to see if the record has been updated at
another workstation.

Also, this is just a pet preference of mine, but many, many subfiles are
well under 9999 records.  In all of those cases I would use a load-all
subfile.  Its just easier, at every level.
 
---------------------------------
Booth Martin
http://www.martinvt.com
---------------------------------
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 03/09/05 10:16:11
To: 'Midrange Systems Technical Discussion'
Subject: RE: Single Page/Expanding/Load all subfile USAGE
 
Well this should be on the RPG list but, I would do a page at a time with
position to.  Just remember to load the subfile with out locking the
records.  I like to read one extra record so I can set the more/bottom
correctly.  I also like to retain the RRN or some data base forced unique
key to chain out and do the necessary update.  You can even keep the
original data in a multi-occurrence data structure for such thing as
changing the unique key or auditing.
 
Chris Bipes
 
-----Original Message-----
 
I have a question regarding usage of Single page/Expanding subfile/Load all
subfile.
 
The program i need to write is supposed to have an update subfile.The number
of records may exceed 9999.
Which type of subfile should one go keeping in mind performance, record
locking , retention of changed values  issues.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
 
 
.