Jamie,
I fully agree with you if you or I were writing a program and were in
position to point out flaws in the logic or possible risks as we see them.
In that case we would be in a position to get replies in real time and act
(write the program) accordingly .
I *always* look for "what if"s when I write a program, pointing out to
client possible, traps. About half of the times I get "don't worry about it
...." and the other half "Oh, I didn't think about it, yes do it". More so,
even when get "don't worry about it", I always allow for it, transparently,
because in many cases the client will change his/her mind or it becomes an
issue during testing.
However, this is not the case here. Sure we should point out possible
negative consequences when we see them. Having done that, it is up to the
person who ask the question to evaluate the relevance of our recommendation
to his/her particular requirements. The fact that this is a medical issue
makes no difference. I bet you that there have been many question here that
were related to medical applications and we did not know about it. Are we
going to ask every "askee" for the type of application his/her question
relates to before we answer the question? of course not.
The examples in your link are illustrations of bad management and lack of
effective testing, none which is of our concern here.
However, may have to agree to disagree and leave it at that.
Regards
Jacob
Jamie Collins said:
David and Jamie
Looking at the top left corner of my screen I see
"Microsoft.Public.Access",
I can't see anything to suggest that I am in medical related Newsgroup
I think that we are digressing from the issue. We have already made clear
the risks associated with the approach as *we* understand it. We have no
idea whatsoever, nor we should , how the codes are entered and what
checks
there are, if any, to ensure their correctness.
To talk about life threatening situations is really carrying it to far.
We
don't even know how and for what purpose the translations of the codes
are
used.
In short, it is not our business!
I should have said [OT] but I think it is an important issue. It
*always* genuinely worries me when I see someone apparently at the helm
of a life critical system asking for help in these groups. That's why I
think we (collectively) should always seek to give the best advice e.g.
fix the design flaw rather than workaround with a kludge etc. I'm
always reminded of this war story:
http://groups.google.com/group/comp.databases/msg/9690dda73900ea4f?hl=en&
Jamie.