× 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.


  • Subject: RE: Detecting if changes were made to a screen
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Mon, 22 Mar 1999 12:32:20 -0800

You could use the CHANGE keyword at the record format level.  It's not
foolproof but it errs on the side of caution.  
DDS manual sez:

 The format of the keyword is:

 

   CHANGE(response-indicator ['text'])

 

 The MDT of an input-capable field is set on when the display station user

 keys into the field, or when your program selects the display attribute

 (DSPATR(MDT)) keyword for the output operation that displays the field.

 If the MDT is set on using the DSPATR(MDT) keyword, the data in the field

 may not have changed even though the MDT (and hence the response indicator

 specified for CHANGE) is set on.  Also, note that the MDT is set on even

 if the work station user keys the same data in the field as was initially

 displayed (such as typing into a blank field and then blanking the field).

 


> -----Original Message-----
> From: Rob Berendt [mailto:rob@dekko.com]
> Sent: Monday, March 22, 1999 11:24 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: Detecting if changes were made to a screen
> 
> 
> Can you create an externally defined data structure using the 
> screen file?  
> Use the RENAME, or PREFIX, options, if necessary.  Then 
> perhaps you could compare.
> 
> 
> 
> 
> as400mail@smtpmail.nationcredit.com on 03/22/99 02:09:45 PM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:    
> 
> Subject:      Detecting if changes were made to a screen
> 
> Short of saving multiple input-field data to saved fields, 
> and then continually
> comparing all the input fields to the corresponding saved 
> fields, is anyone
> aware of a more simple way to detect if the user has made any 
> changes to fields
> on a displayed screen (record)? In other words, I want to 
> display a screen
> record, and then monitor if the user has made any changes to 
> the fields. If so,
> process one way, and if not, process an alternate way. (This 
> is NOT a subfile,
> simply a displayed screen (record).) I know I can"READ" the 
> screen, but what do
> I compare it against? In D-Specs can I create a dummy "screen 
> record" using the
> "LIKE" keyword? (I'm working in RPG-IV, V3R2)
> 
> TIA,
> 
> David Stobberingh
> Nationwide Credit/Phoenix, AZ
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.