Good idea to have a flag if the error should be logged: if you have several logs (eg 1 for user, 1 for tech stuff), it would be good to say just where it should log.
Also need to be able to pass data to show in the message: eg Customer xxxx not on file. Perhaps pass up to 3(?) parameters which could be included in the message. On 10 February 2011 11:23, Dan McGrath <dmc...@imb.com.au> wrote: > That only holds if you have implemented it wrong. Spend some time to > think about how you would implement it. > > 1. Have a subroutine/function which handles the error. That is, it > displays it as appropriate, as well as logging details as required. You > pass it an error number and optional text for the user and optional text > for the log. > > 2. In the user text, you always include the error number. This makes > tracking it back to the exact code location easy as pie [find 'CALL > MyErrorSub(88,'] > > We do it with one of our online systems and it is a damn site easier to > maintain then other systems using the 'old-school' methodology (ha!) of > error reporting. > > > I see so many people blame the general idea of something for the issues > they have, rather than the incorrect way it was implemented. A little > thought into future maintenance/usage goes a long way... > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of > fft2...@aol.com > Sent: Thursday, 10 February 2011 9:16 AM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] Clear Message Initiative - Logging Errors to a U2 File > > > > Here's the problem I see with moving messages out of the code. > > It's perfectly fine *if* you have a developer environment of some kind > that automatically pulls in messages while you're reviewing code. > However in my experience, very few sites have anything close to this. > > As the next one to come along and maintain the code, I have, on the one > hand, a user saying "I have this message that says Error in Back-Order > Received Quantity" and on the other hand, I have code, which I didn't > write, which refers to 25 different errors, all external to the code :) > > Now I have to sit and look up each error code to see which one of them > *this* one is, so I even can figure out what part of the code is > complaining and about what, and how to try to fix it. > > > > Been there, done that, got the T-shirt to prove it. > > So I'd say you need the environment update before the decision to start > shifting the control elements out of code. > It's fine for the original developer. It's a nightmare for the next > developer. > > W > > > > > > > -----Original Message----- > From: Kate Stanton <k...@walstan.com> > To: U2 Users List <u2-users@listserver.u2ug.org> > Sent: Wed, Feb 9, 2011 12:57 pm > Subject: Re: [U2] Clear Message Initiative - Logging Errors to a U2 File > > > Another thing we plan to do with messages some day is to set them up > > in a messages file, so different languages can be easily handled. > > > > It would also be nice to be able to maintain the message without > > program change - makes sense. > > > > On 10 February 2011 09:02, Bill Brutzman <bi...@hkmetalcraft.com> wrote: > >> Thanks to Susan Joslyn for the excellent article on the "Clear Message > > Initiative. I just received my copy of the magazine in the mail today. > >> > >> It happens that over the weekend, I was reading "Code Complete 2" by >> Steve > > McConnell of Construx. Following an idea in Code Complete... > >> > >> Yesterday, I told my boss that I am planning to enhance the clarity of > >> our > > error messages, send a workflow message to others who would need to know > about > > that problem and also to LOG THE ERROR MESSAGE to a U2 file, user, time, > date > > etc. > >> > >> --Bill > >> > >> _______________________________________________ > >> U2-Users mailing list > >> U2-Users@listserver.u2ug.org > >> http://listserver.u2ug.org/mailman/listinfo/u2-users > >> > > > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > ########################################################################################### > The information transmitted in this message and attachments (if any) is > intended only > for the person or entity to which it is addressed. The message may contain > confidential > and/or privileged material. Any review, retransmission, dissemination or > other use of > or taking of any action in reliance upon this information by persons or > entities other > than the intended recipient is prohibited. If you received this in error, > please > contact the sender and delete the material from any computer. > > The intended recipient of this e-mail may only use, reproduce, disclose or > distribute > the information contained in this e-mail and any attached files with the > permission of IMB. > ########################################################################################### > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- Kate Stanton Walstan Systems Ltd 4 Kelmarna Ave, Herne Bay, Auckland 1011, New Zealand Phone: + 64 9 360 5310 Mobile: + 64 21 400 486 Email: k...@walstan.com _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
