|
I think one of the big problems is that programmers are really big on
putting all the controls into their 5250 programs.
One of the biggest examples is many people loathe using database
constraints such as Referential Integrity, check, and otherwise, or
trigger validation. Their concern (with some validity) is that they can
do the check on the 5250 and better guide the user through entering the
correct data.
I'd argue for both. Use the constraints and the triggers. Then, if the
UI developer wants to trap for those, adopt the mentality used by the
people mentioned above, or both, they can do so.
With the constraints and triggers you can ensure that the UI developer
doesn't corrupt your data. Or at least mitigate it to some degree.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.