× 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: Language enhancements (was CF spec)
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Mon, 2 Aug 1999 08:49:07 -0700

I'm of two minds.  On one hand it would be really nice to isolate the
validation logic and cut indicator use to a minimum.  It could make
maintenance easier since the logic of the main program wouldn't be obscured
by the validation logic.  OTOH the validation program might have to know at
least as much about the variables on the screen and in the main program and
their relationships as the main program.  Could make for a long parameter
list.

> -----Original Message-----
> From: James W. Kilgore [mailto:qappdsn@ibm.net]
> Sent: Monday, August 02, 1999 12:56 AM
> To: rpg400-L@midrange.com; midrange-L@midrange.com
> Subject: Language enhancements (was CF spec)
> 
> 
> Hi all,
> 
**************   SNIP  **********************************
> 
> I would like to see a new field level keyword in DDS: VCP
> (Validity Checking Program).
> 
**************   SNIP  **********************************
> 
> The tricky part, to make this work really well, would be to
> make available the entire display record.  Often times one
> would need to know the value of other variables beyond the
> one being tested in order to perform a proper validity
> check.  Like I would need to know the sales order type to
> properly qualify payment terms.  Throw in some
> appropriateness testing above mere hit/no hit on code
> lookup.
> 
> I would be content to specifically code order type as a
> "also pass" variable to the terms code VCP.
> 
> But then again, I have to leave something for RPG to do ;-)
> 
> Something like this, IMHO, would be a great candidate for a
> user written service program to enforce data entry rules.
> Preemptive instead of reactive like a trigger.
> 
> Any thoughts?
> 
> 
> 
> +---
> | 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.