jm.hwsn
jm.hwsn at gmail.com
Mon May 2 15:58:53 CDT 2011
Thanks, I appreciate it. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman Sent: Monday, May 02, 2011 3:27 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Store accdr File Locally or on a File Server? Jim, Mines a little more simplistic then most as I rely on the user to actually execute the batch file, but below is one of the more complex ones I do. The version check is built-into the apps. At startup, I check a local table vs one that is in a copy of the FE up on the server. If the two don't match, I message the user and quit the app. They double click a short cut then to "update", which executes the batch stored on the server in the same location as the "master copy" of the FE. I've meant for a number of years to automate it a little more, but I've found that there is a lot of flexibility in the simplicity of it and just never seem to get around to it. HTH, Jim. ECHO OFF @ECHO. @ECHO. @ECHO Checking for application directories... @ECHO. IF "%HOMEDRIVE%" == "" SET HOMEDRIVE=C: IF "%HOMEDRIVE%" == "H:" SET HOMEDRIVE=C: IF "%1" == "" GOTO DEFAULT SET HOMEDRIVE=%1 :DEFAULT @ECHO ON %HOMEDRIVE% CD\ @ECHO OFF if not exist "%HOMEDRIVE%\Program Files" mkdir "%HOMEDRIVE%\Program Files" if not exist "%HOMEDRIVE%\Program Files\Traverse Custom" mkdir "%HOMEDRIVE%\Program Files\Traverse Custom" @ECHO. @ECHO. @ECHO Copying application files... @ECHO. COPY "P:\Traverse Custom\TM\TM.MDE" "%HOMEDRIVE%\Program Files\Traverse Custom" COPY "P:\Traverse Custom\TM\TM.ICO" "%HOMEDRIVE%\Program Files\Traverse Custom" COPY "P:\Traverse Custom\Update.ico" "%HOMEDRIVE%\Program Files\Traverse Custom" COPY "P:\Traverse Custom\vbSendMail.dll" "%HOMEDRIVE%\Program Files\Traverse Custom" COPY "P:\Traverse Custom\XYRLogoMenu.BMP" "%HOMEDRIVE%\Program Files\Traverse Custom" COPY "P:\Traverse Custom\IDSLogoMenu.BMP" "%HOMEDRIVE%\Program Files\Traverse Custom" @ECHO. @ECHO. @ECHO Setting up environment... @ECHO. "P:\Traverse Custom\SetClientEnv.EXE" TM %HOMEDRIVE% "C:\Windows\System32\Regsvr32.exe" "%HOMEDRIVE%\Program Files\Traverse Custom\vbsendmail.dll" /s rem rem Install mswinsck.ocx if local intall. If TS user this has already been done. rem rem rem ************ rem if NOT %HOMEDRIVE% == C: GOTO EXIT COPY "P:\Traverse Custom\mswinsck.ocx" "C:\WINDOWS\SYSTEM32" "C:\Windows\System32\Regsvr32.exe" "C:\WINDOWS\SYSTEM32\MSWINSCK.OCX" /s :EXIT -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jm.hwsn Sent: Monday, May 02, 2011 09:39 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Store accdr File Locally or on a File Server? I've heard about this and I know it's the preferred method. But how do you do it? I've played around with batch files but I still can't seem to get it right. Would someone please post the script. Thanks, Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins Sent: Sunday, May 01, 2011 10:30 PM To: Access Developers discussion and problem solving Subject: Re: [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. ____________________________________________________________________________ ___________ -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com