Hi. Regarding the Prescription Writer causing very slow painting of the window (minutes long for our XP SP3 clients), I recently sent to one of your Help Desk supervisors (via email) a very long description of some of the "under the hood" issues that seem to be causing this problem.
In our case, it has to do with the AC client spewing out hundreds of SMB packets to the server, and I stated that I believed that all such packets referred to a request by the client to either "lock" or to "read" the tiny file on the server which is stored (on our server) at C:\AmazingCharts.xml I also reported that "something" is causing this file to get continuously corrupted. Three binary bytes (non-ascii characters) get inserted at the very start of the file.
I offered to help anyone on your staff to debug this issue further, to run whatever tests you want me to run, etc., but so far I have not heard back from anyone. I also supplied my direct contact email address. More than a week has passed since I sent my first email directly to you, Dr. Bertman (via the account of Dr. Westafer), and we are nearing one week since I sent a second email containing all the details to a Help Desk supervisor who promised to send it along to the developers.
I now know that I should have used the AC facility for submitting a bug report, and I apologize for going through you and the Help Desk to pursue this issue, because I was ignorant of the "report a bug" facility offered directly within the client itself. Having said that, I sure would like to know if you would be willing to take advantage of my time and expertise to find out precisely why so many packets fly out of the client and why the C:\Amazing Charts.xml on the server is continually getting corrupted. E.g. did you know that even after the Prescription Writer finally settles down, that a simple mouse movement within that window once again causes hundreds or thousands of the same packets mentioned above, to once more fly out of the client and over to the server?
I will be more than willing to help, given that my doctor and her staff have suffered from this problem ever since January, 2011 ... and I am sure therefore that this problem did not begin with the release of Version 6.
Personally, I suspect the .NET framework that was targeted for your code during the build process. But I have no way of verifying that.
