Dale,
First of all, bottom line: Yes, Amazing Charts needs a complete overhaul. Will that ever happen? I am not counting on it. We are most likely going to migrate from Amazing Charts to Athena because, just as you said, AC "used to work better". My doctor has been pulling her hair out over AC issues that started a little over a year ago. I only entered the picture after she started losing her hair, so I don't have any experience with AC working swimmingly, but I am willing to believe that it used to.
I am leaning heavily toward your initial hunches. It is almost certainly NOT his userid (his login) that is being targeted for "malpractice" by Amazing Charts. It IS almost certainly the case that, if everyone else who tries the same computer does not have these problems, then it is in the manner in which he is "moving too fast" for Amazing Charts. I have certain users in my group who do the same thing.
However, although you say that you do NOT have his problems, it sounds like it is also true that you are using AC in a different way. You are "reviewing" what has already been input. A lot of the crashes or stupid "Type 13 mismatch" boxes that I have heard reported by my users come about when they are entering data, not when they are simply reviewing it. Yes, it is true that it happens when they click somewhere, but they have also already entered data somewhere else ... I think.
So, your best bet is to make sure that someone who "clicks the same things that he clicks on the very same computer" does NOT have the same problems that he is experiencing.
But it is a fact that AC, all the way up to v6.1.1 crashes (completely goes away) way too often; and sometimes on quite fast machines. I recently upgraded to the v6.1.2Beta over a week ago, and I have not heard of any problems, but I cannot be sure because my users often refuse to report each such problem throughout the day, because they "just want to do their work", which is understandable too.
If you really believe that other users are performing chart updates to perform the same tasks that he is performing, then you would have to ask them to perform those tasks for the entire day on the same machine that he is complaining about.
If you have already done that, and if they swear that they simply do not have his problems, then it is almost certainly the speed with which he is clicking all over the place, and/or it could also be the case that not only is he clicking fast but that he performs the operations in an order that is different than any other user.
I am 99.99% sure that his Amazing Charts userid is NOT the cause of the problem.
From everything that I have seen that goes wrong with AC, I would not be at all surprised if, by clicking fast, the server "can't keep up" in the following sense: Your first click sent a message to the server, and to perform the task for the first click, the server had to "lock a resource", probably down at the SQL level. The second click came in so quickly that the resource was still locked, and when the server attempted to execute whatever it needed to do, it got an error from the SQL server saying that the resource was still locked. One microsecond later, and everything would have worked just great.
The tough part of "debugging" this (and I have done it before!) is that you would have to put a "packet tracer" like WireShark on this machine, and simply allow it continue monitoring packets until his error occurs. Just like everything else, WireShark is "easy if you know how to use it". But it is remarkably tedious to examine the packets afterwards, and there is no guarantee that, with all the details that you find in the packets, that you'll find the problem.
If anyone knows much about examining problems on the server side by viewing whatever logs get logged by SQL, it would be helpful to see such a post! That is pretty much all that the "AC Server" is; it's just an SQL server that maintains tables specific to AC.
Greg
