Jim Dettman
jimdettman at verizon.net
Tue Sep 13 14:36:10 CDT 2011
John, Source code stripped out, so yes that would be compiled. If that's done, no changes can be made to the code and the code cannot be viewed. If you want to be able to make code changes on site, the alternative would be to distribute as normal, but put a password on the VBA project file. That would be enough to keep the mildly curious out, but still let you make changes on site if needed. And BTW, I see the other Jim posted with more or less the same idea before I did (he suggested changing the extension on the file to .accdr, which also forces runtime mode in 2007 and up. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, September 13, 2011 02:43 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Runtime when full version is installed Jim, When you say distribute as an mde I assume you mean "compiled"? John W. Colby www.ColbyConsulting.com On 9/13/2011 12:42 PM, Jim Dettman wrote: > John, > > No need for the run-time. > > Distribute as a MDE and use the SysCmd(acSysCmdRuntime) call to determine > if it started in run-time mode and if not quit the app. > > Then give them a shortcut on the desktop with the /runtime switch. > > If they use anything other then the shortcut, they go no where. > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Tuesday, September 13, 2011 12:18 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Runtime when full version is installed > > As a non-profit they got something like 50 licenses from Microsoft for > almost nothing. They want > the full version on the employees machines so that they can use all of the > other office applications > and all be using the same version to do so. > > I don't want them using the full version on the Access application simply > because is exposes the > application. I will probably go with a "compiled" version (MDE) once it > stabilizes but for now > using the runtime will help me keep users where they belong. > > John W. Colby > www.ColbyConsulting.com > > On 9/13/2011 10:15 AM, Gustav Brock wrote: >> Hi John >> >> Non-profit and full Office 2010 doesn't match costly wise. Are you they > need Access on all machines? We've never had a client - profit or none - > with that demand; we always use the Office 2010 for home and small business > with the cheap PCK license. >> >> /gustav >> >> >>>>> jwcolby at colbyconsulting.com 13-09-2011 16:01>>> >> I have a small (non-profit) client that wants me to install full office > 2010 on all of their >> employees systems. However I want my Access App to run under the runtime. > Mostly just for that >> additional security of not allowing them access to design time stuff > unless they intentionally open >> the app under the full version. >> >> I have installed the runtime on other machines but I do not remember if > the runtime install allows >> me to set the destination (install) directory. >> >> Is anyone using the runtime? Any tips or tricks for this scenario? >> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com