My last post was so long that I decided to try to summarize it:
Where might the problem(s) lie?
(a). There could simply be a bug in the AC Client code.
(b). There could simply be a bug in the .NET Framework 4.0 as distributed by Microsoft.
(c). There could even simply be a bug in the AC Server code whereby, when the client attempts to access "C:\Amazing Charts.xml", the server-side bug corrupts that file. This could then trigger the AC Client to "go crazy". It might be trying and trying to access a "correct" version of C:\Amazing Charts.xml on the server, only to find, time and time again that the access is failing. So, maybe it tries hundreds of times before it gives up.
d. There could be a bug in the "development and build" cycles, whereby the developers are developing with one version of .NET Framework but the "builders" are then building and releasing an AC Client version that is built with some other .NET Framework.
Honestly, only the AC people can check out these possibilities.
(e). But I am SURE that if AC is supposed to be shipping .NET Framework 4.0 with each release of the AC Client, I am SURE that there is a bug there! I say this because, as I stated before, when I install the AC Client, the .NET Framework 4.0 does not magically appear on my system! Their installer might be installing it in the "wrong" place. They might be installing it, but not installing it with the proper registry keys. The fact is that 4.0 does NOT show up with 3.5 and all the frameworks in the Windows Registry.
In order to determine if my AC Client will use .NET Framework 4.0 if it is installed (by me), I might have to resort to the one thing that I did not want to try:
I might DELETE all the other versions of .NET Framework that exist on my system, and leave only .NET Framework 4.0 there. Then, I can try to run the AC Client one more time, just to see what happens.
(f). What I am getting at is that there is some possibility that for every client machine that is suffering from a very slow paint for Prescription Writer, the following is true: They downloaded and installed AC Client 6.x (even 5.1.9), and the installer noticed that .NET Framework 4.0 was not yet on their system. So, the installer then "tried" to install .NET Framework 4.0 ... and it failed! If the AC Client is now only designed to "run properly with .NET Framework 4.0", then each such client machine on which 4.0 was not correctly installed might (might!) have the slowness problem.
If others who are experience "really dramatic" slowness (not 2 or 3 seconds) want to check if they have .NET Framework 4.0 installed, that might help to answer this question. Nevertheless, I guess I will have to muster the courage to DELETE all other versions of .NET Framework, and see what happens.
Greg (MaxJammer)
