Mario, FYI, I should point out that Cedric is a Best Practice beta tester who uses beta builds live in his everyday practice, consequently he is likely to occasionally need to roll back a build. Although this feature is not disabled in the general release version of the program, I am not aware that it has ever been needed by any non beta tester.
Frank Pyefinch -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mario Ruiz Sent: Tuesday, 3 July 2007 8:41 PM To: General Practice Computing Group Talk Subject: Re: [GPCG_TALK] Wish list- Medical Software Marvelous?, Why would anyone code a "Downgrade" in an application? It speak tons of the Unit/Apps Testing process quality in the first place, and then leave it to the user to clean up the mess. Is that marvelous? Is one thing to roll-back data updates (ie rdbms), but a totally different thing to roll-back an application upgrade. if testing is not complete, one never releases the upgrade it in the first place. I'm not a purist but to me that really sucks. mario Cedric Meyerowitz wrote: > That is what happens to BP users too. Further in the unlikely event > that a program update has a bad bug that was missed, with a double > click we go back to the previous edition - thus no down time, trying > to uninstall the new program & then installing the old one, crossing fingers etc. Marvelous. > > Cedric > > _______________________________________________ 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
