Ferdinand, thanks for pointing that out. If you can do so, definitely download Wireshark from the web and just make sure that it's running (tracing packets) before you click on the button that brings up the Medications list or the Rx Writer.
What I just wrote is misleading in the sense that you know already how to set things up for tracing packets after Wireshark starts up. Although it is extremely easy after you do it once, the problem is that it can seem very mysterious as to what to do the first time.
If I get a chance, I will try to compose a very short tutorial on: 1. Where one can download Wireshark 2. What settings you need to establish (very few) in order to get it running. 3. What "filter" you should establish so that you don't have to view ALL packets, but rather only those packets that pertain to your client's communication with the Windows Server.
One of the reasons why it's important for me to encourage others to trace the communications using a packet tracer is very simple: You "slowness" issues might not be caused by the same anomaly. Offhand, I would have to suspect that Ferdinand's problems are NOT the same as mine. I only say this because our Windows 7 boxes have NO problems whatsoever, and yet Ferdinand's Windows 7 boxes DO experience a slowness problem.
So, it's important that other people attempt to trace the packets, in order to see if, right after clicking to get the Rx Writer or Meds List, you see thousands of packets flying by between your machine and the Windows Server.
Another possibility (if you want to trace the packets) might be to use wireshark and to look for a "quick tutorial" on the web, maybe even on YouTube. But I will try to find the time to write something up.
