|
I'm with you on this one. Any field editing that directly or indirectly
controls what data is put in a file, I put in editing routines in my code -
and I dare say, you should probably encapsulate as much of it as prudent in
callable functions/subprocs, so they may be re-used as needed.
I do, on the otherhand, do some DDS field checking for subfile 'option'
codes and the like.
for instance:
S1OPT VALUES('2' '3' '4' '9')
this seems very reasonable to me. The only time I wouldn't do the above is
if the valid options could change based on outside factors.
rick
-------original message----------------
Are there any good reasons to validate in DDS?
I have come to accept as my "programming style" to
NEVER validate in DDS. And after this discussion, I
believe that may be the correct decision...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.