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



John's code snippet is a perfect example of a procedure imitating a
subroutine. I personally would never do a validation subroutine as a
procedure, there is no advantage. Nothing is declared locally to the
procedure, all variables are global to the module.

How do you separate your business logic from your display logic, then? How to you write your business logic (and by all accounts, validation is business logic!) so that it can be re-used from both your GUI display and your green screen?

If I have three procedures in a module and they each have to validate parms,
then all of the parms to those procedures have to be global, or I can pass
the parms to the validate procedures, or I can use 3 subroutines within the
scope of the respective procedures to validate its parms locally. So a
subroutine becomes sub-sub procedure local to it's parent sub procedure.

Which fields do you validate in each subprocedure? How do you determine that?

Is there a reason you need to validate more than one field, or a set of related fields, in a single subprocedure?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.