Doug Murphy
dw-murphy at cox.net
Mon Nov 14 11:35:52 CST 2011
Rocky, I think the runtime installer is more robust and would work if you never had to deal with other versions of Office being on the client machine and the various security issues with Windows Vista and 7. What Sagekey brings to the game is having a system that can accommodate whatever the customer has and play nicely with it. The new Sagekey scripts work with MSI and don't require Wise as I understand. We are still using the Access 2000 runtime and scripts. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Monday, November 14, 2011 8:12 AM To: 'Access Developers discussion and problem solving'; 'Off Topic'; List Subject: [AccessD] Access 2010 Deployment (cross posted) Dear Lists: I am considering upgrading a commercial product from Access 2003 to Access 2010 (loathe as I am to develop in 2010 - I guess it's time). Although most of the target market has Office with Access, so I can distribute an mde, some do not so I have always had a run-time version available as an option. I have used the Wise/Sagekey combo for this purpose for may years. (IIRC, the market for Sagekey was motivated in no measure by the poor implementation of run-time deployments in A2000 and A2003.) I have seen references to a run-time deployment in A2010 being much improved. If I can avoid purchasing the Sagekey 2010 script and using Wise I would prefer that - it would make life much simpler. So I am looking for experiences/comments/feedback/benefits/drawbacks, etc., on the effectiveness of the A2010 run-time deployment. MTIA, Rocky Smolin Beach Access Software 858-259-4334 www.bchacc.com <http://www.bchacc.com/> www.e-z-mrp.com <http://www.e-z-mrp.com/> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com