mickey71 said:
I aplogize if I somehow insulted you in one of my posts. Your post took an
irritated tone. I am somewhat new to using discussion groups and apparently
I have made a "faux pas", judging from your last response.
I did not continue searching your posts for other threads since I had posed
a specific question to you in response to your last post to me and I was
awaiting your response to that particular question. I guess that I should
have...as I said I am trying to learn. Your criticism taken and appreciated.
Yes. Definitely do not *expect* a reply. This is a newsGROUP.
Replies can come from anybody or not, depending on people's
interests and abilities. In particular, if questions or problem descriptions
are vague (or too hard to deal with easily) you may get no reply at all.
Specifically, I wonder what further information I should have provided to
you so that you would take interest in my issue. You said that it was " such
unexciting feedback that I wasn't inclined to follow up with any more ideas."
I am *not* trying to be sarcastic, I am just trying to learn what would be
helpful for me to list in my posts. I *did* try everything, step-by-step
that you listed and I was unsuccessful in making any difference to my
problem. There were no spefic problems that I encountered in executing the
steps you provided...everything went fine, it just didn't fix my problem.
Since there were no problems with your steps, I didn't have anything other to
report than "tried all the suggestions you listed".
Understood. I guess I should accuse myself of "jumping into this thread"
too. As I wrote I was just trying to clarify some details for you on the tack
which had been taken. My particular interest is diagnosing symptoms
rather than just guessing if some standard general repair procedure
can be thrown at a problem symptom. _Usually_ my suggestions include
actions which I would take as diagnostics. That implies that observations
should be made and reported as feedback or if the significance of them
is clear reports may come back that a solution has been found as result.
Too often the "tried everything; didn't work" response is from someone
who is not interested in trying to learn how to help himself. OTOH if all that
helpers are doing is shooting their favorite ammunition (e.g. repair suggestions)
they may be either "out of bullets" or reduced to dragging out the heavy artillery
(e.g. reinstall, etc.), which is roughly analogous to demolishing someone's
house as a response to a stuck door and then saying: "Please rebuild your
house; that should fix your stuck door problem." <g>
After reviewing your problem description I'm not sure that there is a problem
which can be dealt with using a repair methodology. E.g. your symptoms
could also be explained by the hypothesis that there are multiple servers
for your application and one or more of them has not been updated with
the latest changes. So, then, every so often you get served the old version
of the scripts and when one of the other newer pages attempts to use the
newer versions of them there is a script error. Etc.
One way to deal with such a scenario would be to press Ctrl-F5 when it
happens and hope that the requests which that generated would get handled
only by servers which contained both the new versions of the pages and their
components. Meanwhile using the options which Frank mentioned for
disabling script debugging, etc. would minimize the disruption any such
errors would cause.
In that case the ultimate solution for the problem would rest with the server
operators and you would either have to wait for them to fix things or write
to them to try to expedite such changes.
HTH
Robert
---
