Stuart McLachlan
stuart at lexacorp.com.pg
Sun May 1 23:10:45 CDT 2011
Yep, that's what I do as well. -- Stuart On 1 May 2011 at 22:58, jwcolby wrote: > I place them on the local PC simply because the time to get the pieces > and parts is usually faster. > > I use a batch file which just copies the FE from a production > directory on the server every time they open the fe, but there are > utilities that check for the version and only copy if newer. > > John W. Colby > www.ColbyConsulting.com > > On 5/1/2011 10:26 PM, Brad Marks wrote: > > All, > > > > Background - Small firm, approximately 25 PCs. > > > > Currently no change control software, but we could put together > > something to do this. > > > > We have an Access 2007 application that has a Front End that is > > about 20 MB. > > > > We have set up a folder for each user on the file server so that > > each user can have their own copy of the Front End. > > > > We are debating whether we should store the Front End in each of the > > Users´ Folders on the File server or store the Front End on the > > local PC´s hard drive. > > > > Storing the Front End on the file server simplifies our procedures > > to release new versions, but it appears to takes several seconds to > > initiate the application when it is stored on the file server. > > > > Storing the Front End on the local PC´s hard drive would reduce the > > application initiation time, but this approach would result in more > > complicated procedures when new versions of the application Front > > End are released. > > > > Is there any "Rule of Thumb" to consider in this decision (such as > > "any accdr over X MB should be stored locally"). > > > > Are there other issues that we need to keep in mind? > > > > Thanks, > > Brad > > > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >