Re: Proper handling of subfiles

[Jeff Young <cooljeff913@xxxxxxxxx>]

Doug,
  The way I usualy handle that is to define a Data Structure with all my input 
fields for the subfile line, then define a *dummy* data structure like the 
first.
  In my setup processing, I clear the Detail Data Structure & save it in the 
*dummy*.
  When processing the subfile record, if the Detail Data Structure = *dummy*, I 
turn off SFLNXTCHG and bypass processing for that record.
   
  

"Douglas W. Palme" <dpalme@xxxxxxxxxxx> wrote:
  I have a question that has bothered me for sometime now, regarding how to 
properly handle entry in a subfile.

I will attempt to put this into context of a three field subfile containing 
ten rows.

All three fields are type ALPHA, 5 characters in length....

Using RPG I can check the subfile to see if there were any records that were 
changed, IE: added and can then verify the data before writing it to the 
file. In theory that is fandamntastic. However what is the proper way to 
handle say the second row of data where the user initially entered something 
and then decided naw, isn't needed or was a mistake so they removed it. 

If I understand how the next changed record works, it will come up with both 
lines 1 and 2 even though 2 really has not been changed.....IE: no data 
contained within.

Suggestions? Or do I need to check each possible line and if there is no 
data, end the processing.

Douglas

If you bought it, it was hauled by a truck - somewhere, sometime.