[AccessD] Store accdr File Locally or on a File Server?

_______________________________________________________________________________________

Note: This e-mail is subject to the disclaimer contained at the bottom of this message.
_______________________________________________________________________________________



This is the same approach I use.  A script checks the version number of the local FE vs the expected FE version no stored on the server. If they are different it automatically removes the local FE and downloads a new one and then opens it.  The user never even knows about the update process.  All they do is double click on the database FE icon as usual and the rest happens seamlessly in the background.

cheers
Darryl.

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Monday, 2 May 2011 12:58 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Store accdr File Locally or on a File Server?

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
_______________________________________________________________________________________

The information transmitted in this message and its attachments (if any) is intended 
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in reliance 
upon this information, by persons or entities other than the intended recipient is 
prohibited.

If you have received this in error, please contact the sender and delete this e-mail 
and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or distribute 
the information contained in this e-mail and any attached files, with the permission 
of the sender.

This message has been scanned for viruses.
_______________________________________________________________________________________