Thinus, " hoe gaan dit" Ask Tech support, if they will be prepared to come & help you the same day, if the new version mucks things up. Is worse than what you have now etc. Depending on their answer, you'll know whether to jump in or not.
Cedric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thinus van Rensburg Sent: Tuesday, 5 June 2007 12:13 PM To: [EMAIL PROTECTED]; General Practice Computing Group Talk; Uncensored mailing list for Oz GPs Subject: [GPCG_TALK] Update on my MD3 crashes After numerous e-mails to HCN support I finally go a call from a senior techie this morning - I assume because I started copying Andrew Magennis in on my mail. Bottomline: 1. The crashes are known to them as two of their beta testers have the same problem 2. The could not reproduce teh problem in their lab at HCN and it seems that they have no idea what causes it. 3. The beta testers who have the same problems that we have don't have it when testing MD 3.6 and the assumption is therefore that this update (due in July) will fix the problem My dilemma is the following: I usually wait at least several weeks before running a major update as the early uptakers usually unmask a heap of problems that the beta testers did not find and I wait until the first patch has come out. Do I now bite the bullet and MAYBE fix my current problems (that HCN apparently don't know the cause of and has accdently fixed in 3.6) and expose myself to a heap of new ones by being an early uptaker of the new version? T _______________________________________________ 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
