RE: Detecting when a user hits enter on a DSPF screen without changing anything.

[John Rusling <jrusling@xxxxxxxxxxxxxxxxxxx>]

I'm in the habit of doing what Dennis indicates but with a field by field
comparison.. for the reason that he points out below.  Every edit-able
display file field has a corresponding hidden field for comparison.
(someday I should consider his method, someday...)

John B.


     d testforScreenChanges...
     d                 pr              n
...
...
             when dvInKey = ENTER;
               if gModeSw <> DELETE;
                 AnyChanges = testforScreenChanges();
                 if not AnyChanges;
                   // goto next screen, exit whatever
                 else;
                   exsr @process;
                 endif;
               endif;
...
...               
      //===============================================================
     p testforScreenChanges...
     p                 b
     d                 pi              n
      // Check to see if any screen fields were changed
      //===============================================================
      /free
         if hfVEN#   <> scVEN# or
            hfSUPC   <> scSUPC or
            hfSCAC   <> scSCAC or
            hfTAXS   <> scTAXS or
            hfPODT   <> scPODT or
            hfSHDT   <> scSHDT or
            hfEADT   <> scEADT or
            hfPOTYPE <> scPOTYPE or
            hfWHS    <> scWHS    or
            hfCOMP   <> scCOMP;
            return *on;
         else;
            return *off;
         endif;
      /end-free
     p                 e


> > Is there an easy way, other than by comparing a copy of the field data
> > sent to the terminal with the field data received back, to tell if the
> > user just hit <enter> without changing anything?
> >
> > It sounds like something I've used before, but completely forgotten
> > about.
>
> You mean like the CHANGE() indicator?  The problem with it is that if the
> user changes a value to its original value (like "JOHN" to "JOHN"), the
> indicator will still be set (because the field MAY HAVE BEEN modified.
> Dennis Lovelady