RE: Single Page/Expanding/Load all subfile USAGE

Like the hidden subfile field and use it for unique keys and the like.
Guess just make it one large field to hold the length of the record.  Never
thought of that.  I agree with the load all but if it needs to handle more
than 9999 as mentioned in the original post, it might as well be a page at a
time.  Besides once you code one "page at a time" subfile, you use that as a
template to do the others.  Only file/record format/field names need to
change.

Chris Bipes

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Wednesday, March 09, 2005 8:52 AM
To: Midrange Systems Technical Discussion
Subject: RE: Single Page/Expanding/Load all subfile USAGE


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.