David Kahn wrote

> Al Mac wrote:
>  > So we go into that error message reply list & alter the
>  > rules so that if the user just presses enter, the least
>  > harmful option in general is taken.  We also adjust
>  > phraseology of error message so more users comprehend
>  > what just happened.
>  I see. You mean you alter the text and default replies of the message
>  descriptions in the vendor provided message file.

Right - that is exactly what we are doing.

>  > We do this to scores of error messages in the vendor
>  > package.
>  This is really necessary?

This is an important question that goes to the heart of corporate culture
when software is aquired without solid education for the end users in that
software, and when perception exists that the vendor software is not as good
as it could be.

There was a recent thread where some CEO did not want any more users having
to wait as long as 2 minutes for access to JDE interactive screen.

In my case the area of lowering tolerance is for errors getting into BPCS
data base due to human error that perhaps is avoidable.  I have been
rewriting some programs to try to intercept error conditions before they even
get to the end users, but there is an enormous volume of code & there is also
the notion that the customer is always right in my corporate culture.

They find out that something is doable.
They ask for some change.
My only checks, when I think the change is unhealthy is to make sure all the
players that are impacted are in agreement that this is wanted, and I have
exhausted suggestions for something superior.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
BPCS 405 CD Manager / Programmer @ Global Wire Technologies Incorporated
http://www.globalwiretechnologies.com = new name same quality wire
engineering company: fax # 812-424-6838

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.