As long as it's not forced - my big server that handles thousands of mailboxes and hundreds of thousands of emails a day - I can't afford for it to go down for any reason, so I would want it to be done manually. My small server that handles only a few clients and who are understanding if their mail goes down for an hour or so - no problem with auto updates there. I typically try the new versions there first, and if all is well for a couple of days, I update my big box.
At 11:46 AM 11/25/2009, K Post wrote: >I'd like to chime in that I don't think autoupdates are the way to go. >First, for those of us who have made minor modifications to ASSP for >internal reasons (long story), this would be a huge problem. Second, if >autoupdates are forced, I think you'll actually decrease the number of >installations - there's plenty of real organizations (unlike our non-profit) >that can't stay on the bleeding edge and need to do QA testing on their >own. I definitely saw this in my former life in corporate America. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
