I would have thought the error mentioned by Christopher may relate to the handling of application variables in the client memory space. Another example I recall - At one stage in MD2 there was a neat way of changing the identity of the logged on doctor - if you logged in as Dr A and printed a batch of stored scripts, and the list included some scripts previously entered by Dr B (B's surname had to be alphabetically greater than A's for this bug to operate), then from that time on the program behaved as though Dr B was logged in even though Dr. A didn't have a valid password for Dr.B. This was fixed I think but it leaves in doubt the validity of any progress notes written before the fix.
Tony Peter Machell wrote: > On 24/05/2006, at 8:43 PM, Christopher Wurm wrote: > >> I would have presumed no professional software package could allow >> such an error. How on earth did this get through ? Do we have a >> guarantee it won't happen in MD3. If that could recur, I'd like to >> make a strong case for using something else - in fact almost Anything >> else! > > You've been spoiled by Genie. Errors like this are common in MD2 which > was never designed for network access, and requires constant management > to keep data pollution to a minimum. Unfortunately the file repair is > the only way to fix this sort of thing but is itself the most common > cause of this sort of issue. > > MD3 is much better already and improving rapidly, but the conversion is > not trivial - in fact converting to Genie or Best Practice is more > reliable. > > Peter. > _______________________________________________ > Gpcg_talk mailing list > [email protected] > http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk > > _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
