<div>
Scott, I will check out <a href="http://autofeupdater.com/" rel="ugc">http://autofeupdater.com/</a>&nbsp;and get back to you. Will this work with a MyQL backend. <br />
<br />
The batch file route would be beyond my capabilities<br />
<br />
I have plans to migrate to SQL Server 2012
</div>


<div>
I pulled this off at one client a dozen years ago, lots of code (which I don't have) but works like a charm. &nbsp;<br />
Beats the hell out of walking to dozens of user's desktops to copy over new versions. <br />
Goes something like this: <br />
<br />
(1) &nbsp;In each Access FE app have a table that stores the version number. &nbsp; Use <a href="https://www.experts-exchange.com/articles/12696/Table-Based-Access-Variables.html" rel="ugc">Table Based Access Variables</a> for some ideas. &nbsp; This is your front-end version number. <br />
(2) &nbsp;In SQL Server have a similar table/value. &nbsp;This is your 'Most current front-end version number'. <br />
(3) &nbsp;Create a little VB (or Access) app which does this: <br />
&nbsp; &nbsp;Check the version number in (1) <br />
&nbsp; &nbsp;Check the version number in (2) <br />
&nbsp; &nbsp;If (1) &lt;&nbsp;(2), aka the user has an old version and a new one is available, the VB app does this<br />
&nbsp; &nbsp; &nbsp; Deletes the Access FE app off the user's pc <br />
&nbsp; &nbsp; &nbsp; Copies the newest Access FE app off of a network location somewhere, moves it to user's pc<br />
&nbsp; &nbsp; &nbsp; Runs the 'newest' Access FE app off user's pc. <br />
&nbsp; &nbsp; &nbsp; Closes the VB app<br />
&nbsp; &nbsp;If (1) = (2), aka the user is running the current version, the VB app does this<br />
&nbsp; &nbsp; &nbsp; Runs the current Access FE app off user's pc<br />
&nbsp; &nbsp; &nbsp; Closes the VB app
</div>


<div>
Thanks Jim, it will take me a while to try that out.
</div>


<div>
<blockquote>
 Will this work with a MyQL backend. 
</blockquote>
Yes. The Backend platform is not relevant to the Frontend.
</div>


<div>
I do what Jim Horn talks about.<br />
I've helped others do the same.<br />
Big discussion of my methods with code blocks here<br />
<a href="https://www.experts-exchange.com/questions/28572159/How-to-update-a-local-Access-front-end-via-a-shell-command-within-Access.html" rel="ugc">https://www.experts-exchange.com/questions/28572159/How-to-update-a-local-Access-front-end-via-a-shell-command-within-Access.html</a><br />
<br />
I deploy a script to the client that checks for the existence of the front-end, or evidence of a client-end crash. &nbsp;It then checks the local version vs deployed version and pulls a new copy if needed.<br />
<br />
I have a script that copies the dev version to the deployment location and bumps the version ahead a point.<br />
<br />
I have a couple three scripts that will give the shortcut to the .vbs script the appearance of an Access icon<br />
<br />
Double-click for me to deploy a new version.<br />
Double-click for the clients to open/update.<br />
<br />
Quite nice!
</div>


<div>
Tony's FE Updater, which Scott mentioned, has a lot of features and is worth the price if you use them. &nbsp;There is a video about it here: &nbsp;<a href="http://www.youtube.com/watch?v=s1-OOqvvpxs" rel="ugc">http://www.youtube.com/watch?v=s1-OOqvvpxs</a><br />
The video is really a walk-through of some of what it can do and worth watching.<br />
<br />
and to throw more in on top of the excellent information already given ...<br />
Bill Mosca has a nice article about how to do this yourself here:<br />
<a href="http://www.thatlldoit.com/Pages/howtosarticles.aspx" rel="ugc">http://www.thatlldoit.com/Pages/howtosarticles.aspx</a><br />
Deploying and Updating Front End Database Applications
</div>


<div>
The batch file is actually the simplest solution. &nbsp;Mine is only fourlines and it works for new or existing users since it also makes the directory on their local PC. &nbsp;The database solutions are much more sophisticated and do version checking but they are more difficult to implement than a batch file.<br />
<br />
md c:\ClientMgt<br />
del c:\ClientMgt\AOAClientMana<wbr />gement.acc<wbr />dr<br />
copy \\newfiscal\Afox\AFox\Acce<wbr />ssApplicat<wbr />ions\Clien<wbr />tMgt\AOACl<wbr />ientManage<wbr />ment.accdr<wbr /> c:\ClientMgt<br />
c:\ClientMgt\AOAClientMana<wbr />gement.acc<wbr />dr<br />
<br />
md - make directory - make the directory I want them to use on their C: drive<br />
del - delete the existing copy of the database (if any - this won't error for new users)<br />
copy - copy the FE from the server location to the directory you made on the C: drive - &nbsp;ALWAYS use UNC notation to refer to the share drive to avoid inconsistencies in drive mapping letters.<br />
execute the new version of the file<br />
<br />
The batch file for Citrix is a little more complex since it has to use tokens to refer to user directories. &nbsp;This doesn't use tokens because I am controlling the exact place and name of the folder I want them to use.
</div>


<div>
I do not have the technical capabilities for most of the suggestions so Auto FE Updater is the perfect fit for my problem.
</div>


<div>
If you have the budget, that's great!<br />
<br />
<i>I do not have the technical capabilities</i><br />
You run Access, don't you?<br />
All that there is to the VBSript files is an ADO connection and use of the FileSystemObject.<br />
Nothing earth-shatteringly complex.<br />
<br />
You can code it all within Access, too, but then your launcher fires up Access, which is a fairly heavyweight operation.<br />
But not technically complicated.
</div>


<div>
The batch file doesn't require any programming logic. &nbsp;You simply swap the name of your database for mine and the names of your source and target folders for mine. &nbsp;You must know what file and folder names are to have gotten this far.<br />
<br />
You can then send the .bat file as an attachment and ask the recipient to save it to his desktop. &nbsp;Then he clicks on it to run the process.
</div>


<div>
<div class="content wysiwyg-content">
I have an &quot;MS Access 2010&quot; application with about 10 users, every-time I make changes to the front end I have to update each client PC. <br />
<br />
Is there software I can get to place the updated file in a server folder and when the file is changed the clients will automatically download or link to the new file?
</div>
</div>


I have an "MS Access 2010" application with about 10 users, every-time I make changes to the front end I have to update each client PC. 

Is there software I can get to place the updated file in a server folder and when the file is changed the clients will automatically download or link to the new file?

MS Access Front End Distribition

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.