Hi Everyone,
Hmmm?.
I?m going to make some educated guesses according to some helpful clues, from others. All this still boils down to the source code behind the prescription writer in v6.0.9, and maybe earlier.
PROS:1.) eRx runs better and faster on main (or networked) PC(s) with Windows 7, with very good processor speed (dual or quad core, 2.0 Ghz or faster), and adequate memory (4GB or more).
2.) eRx runs better with improved graphics card (video card) on PC(s) running Windows XP, with very good processor speed (dual or quad core, 2.0 Ghz or faster), and adequate memory (2GB or better).
CONS:1.) eRx runs horrifically slow on PCs with Windows XP, with decent, but single-core processor (P4 2.0 Ghz or better), and adequate memory (2GB or better).
That?s what mostly everyone is saying.
Ok, I?m going to write English and not technical jargon. What I believe is happening with the prescription writer is, it?s trying to draw out each row item in the grid?s view. What I mean by ?draw out? is the source code behind the eRx window is physically trying to draw the grid graphically, along with the querying of data. This is where it?s using more PC resources than it should.
The problem is: with the source code behind the prescription writer module or window. That?s what I believe is putting the toll on hardware. AC programmers would have to tweak the code to make it run, universally faster on both Windows XP and 7. Now, depending on how the code is written, it may not be as simple to fix.
I hope this will help.
