|
On Tue, 9 Nov 2004 15:31:15 -0600, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote: > > From: Steve Richter > > > > It is hard coding. Send an exception back to program "menu01C". No > > matter your religion that is a bad practice that does not contribute > > to bullet proof applications. > > Not if you set the level programmatically at runtime, which is what I > do. Steve, you make a LOT of assumptions about my programming which > make it pretty clear you've never really tried any of this. > > > > there is also the practical matter of one module in the application > > telling the AG shutdown module what has to be shutdown. If the "in > > transit" quantity in the inventory master is changed in the > > expectation of the code at the end of the module moving that quantity > > to the "received" column, how do you tell the catch all AG exception > > handler what it needs to know to undo or complete the transaction? > > First off, if you have written an application where the integrity of > your transaction is in question, AND you've designed the code in such a > way where the module has a failure point between integral updates, AND > you haven't used some sort of commitment control, then you really > shouldn't be writing code for a living. you win! Try to keep in mind that you responded to my post. take care, -Steve
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.