K
Kevin Spencer
Hi Juan,
I certainly did NOT recommend using the System account. You ought to know me
better than that!
I simply objected to the blanket statement that you should NEVER use the
System account. IOW, blanket statements are seldom useful in programming.
What IS useful is to understand the technology well enough to make an
educated decision with regards to EVERYTHING about your app.
The remark about wearing short sleeves was an analogy. It refers to some
churches that think that bibilical statements taken out of context amount to
rules and regulations for dressing. In fact, those statements were made IN
context, and based upon a set of principles. Applying the principles
properly and in context yields good results. Ignoring the principles and
applying statements made in a certain context OUTSIDE of that context yields
bad results.
Now, if this was a forum for ignorant software users, I might be tempted to
make the blanket statement, as the audience would not know what the heck I
was talking about, and therefore, should stick within absolutely safe
parameters. But I'm talking to programmers here (most of us, anyway), who
should understand the technology, and make decisions based upon their
understanding of the technology, not heresay or "official documents" taken
out of context.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
I certainly did NOT recommend using the System account. You ought to know me
better than that!
I simply objected to the blanket statement that you should NEVER use the
System account. IOW, blanket statements are seldom useful in programming.
What IS useful is to understand the technology well enough to make an
educated decision with regards to EVERYTHING about your app.
The remark about wearing short sleeves was an analogy. It refers to some
churches that think that bibilical statements taken out of context amount to
rules and regulations for dressing. In fact, those statements were made IN
context, and based upon a set of principles. Applying the principles
properly and in context yields good results. Ignoring the principles and
applying statements made in a certain context OUTSIDE of that context yields
bad results.
Now, if this was a forum for ignorant software users, I might be tempted to
make the blanket statement, as the audience would not know what the heck I
was talking about, and therefore, should stick within absolutely safe
parameters. But I'm talking to programmers here (most of us, anyway), who
should understand the technology, and make decisions based upon their
understanding of the technology, not heresay or "official documents" taken
out of context.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
