|
Mac asked for an approach to fix the problem. It would require programming no matter what. I offered my opinion that record locks were architecturally unsound. I don't think there's an argument there. You can't use corporate philosophy to measure the strength of a design. Corporate policy does NOT dictate good architecture - it simply decrees whether or not a good architecture is economically viable. As to the realities of whether a given approach is economically feasible or not, that's an issue to be taken up in each individual instance. There's always a way to justify bad programing practices. I just try to make sure that people realize that they ARE bad practices, and that there are alternatives. When management says, "program it this way," I like to give programmers the ability to say, "that's bad programming," and be able to back it up. I recognize reality hurts sometimes, but it's better to have the facts. Joe > -----Original Message----- > From: owner-midrange-l@midrange.com > [mailto:owner-midrange-l@midrange.com]On Behalf Of D.BALE@handleman.com > Sent: Tuesday, June 05, 2001 1:25 PM > To: MIDRANGE-L@midrange.com > Subject: RE: WRKOBJLCK automated API ? > > > With all due respect, Joe, the *USE* of the methods you describe > are clearly > the exception rather than the rule in the real world. Whereas, > most of us are > smart to handle the record locking issues now for any new > development, what > *reasonably* can be done for all the legacy code out there that > was written > without the benefit of our superior wisdom? > > In some cases it may come down to: "You want to spend HOW much > money to fix > something that occurs a few times a year/month/week/day? Just > tell the users > to never leave their desk without the menu showing." Or some such drivel. > > Just my .02. > > Dan Bale > IT - AS/400 > Handleman Company > 248-362-4400 Ext. 4952 > D.Bale@Handleman.com > Quiquid latine dictum sit altum viditur. > (Whatever is said in Latin seems profound.) > +--- | 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 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.