Auto FE Updater

Frequently Asked Questions

Other FAQs - Frequently Asked Questions 2,  Enterprise Edition FAQ and Licensing FAQ

Q: how does the utility know that an update has been made to a file in the server folder?

Q: What about Windows 8?
The Auto FE Updater utility works just fine under Windows 8.   Now there will likely be issues if Access version next runs on the ARM CPU for tablets.   But there is lots of time to figure out that solution and I have a plan.

Q: I'd like to copy files in subfolders down to the users target folder.
You can now use the uncompress files option for this.  A better solution will be coming but it will be at least November of 2011.

Q: Why didn't the uncompress files unzip the contents of the zip file when I was testing?
Q: I'm getting error messages when the user downloads a Zip file such as CRC calculation failed, CRC error, Error in decompressed size or Error writing file but when I ask the user to find the Zip file it's not there.
See the uncompress files page.

Q: My users are getting the following message:  "1184 - It appears you are already running this application.  Please exit and try starting the application again.  A Microsoft Access Record Locking Information (LDB/LACCDB) file was found and could not be deleted. "  What is happening?
The utility is now checking the target folder to see if an LDB/LACCDB file is present.  The problem is that bizarre things can happen if a user is already in the FE database file and if the Auto FE Updater utility needs to copy down the new FE database file over top the old one.  However some folks are telling me that this is a problem.  I've added a check box on the Seldom Used Update form which states "Ignore the 1184 - Already Running App message".

Q: I want to use the RemoteApp feature of Terminal Server.
See the Terminal Server RemoteApp page.

Q: My users are getting the message "The Auto FE Updater is no longer free for use.  Please purchase a license as your trial period is over." "You can contact your support personnel who can immediately set a seven day trial period extension.   You can continue to use this utility."    But I'm not seeing this message.  How can I immediately set the seven day trial period extension?
Go to the File, Tools & Help menu and choose Tools.   Then select Request Trail Period Extension.  

Q: If someone is in the database BE; if I "lockout" while people are in - will that cause corruption in my access file; or will it simply let them finish what they are busy with and only lock out new attempts to access?
Lockout only sets a flag in the config file.  It does not do anything to the Access files.  So yes you can set it and the users already in have an unlimited amount of time to finish.  Any users that try to go into the app will, of course, be unable to do so.

Note that the Enterprise Edition has a Lockout - Create Email to Users feature which allows you to send an email to those users currently in the BE.  Once you go to unlock the database you can send an email to those who were in the database as well as those who attempted to use the app while it was locked out. 

Q: When I open the View users in backend database files form I'm only seeing my name in the list while the other users have a line stating "Problem encountered reading data from log database".
A: You are possibly testing the Auto FE Updater and have two different versions on your server with two different AutoFEUpdater Log.MDB files.   When you are running the newer version the utility is pulling in all the workstation ids from the Access or SQL Server database file but the Auto FE Updater Log.MDB only has your userid in it.   You can see this yourself by opening the AutoFEUpdater MDB file in Access and open the SystemUsers table.   The solution is to open the Enterprise Edition form and change the Auto FE Updater Log.MDB file to point to the active AutoFEUpdater Log.MDB file with all the users in it.

Q: I can't see any connections in the View users in backend database files screen but I know there are lots of users in the SQL Server database.
The DBA or IT administrators must give you explicit permissions to view this data by issuing the following SQL Server command.
GRANT VIEW SERVER STATE TO <your network userid>

Q: I can't see all the users on a Citrix/Terminal Server in the View users in backend database files in the Access backend.
The Access LDB/LACCDB only records the workstation name.   The only way to determine the name of the user is to query the log database file for the last user of that workstation.  This, of course, doesn't work for Terminal Server users.   You need to implement the AutoFEUpdater_ExitApp code as found in the Auto FE Updater Sample Code Vx.xx.mdb in the distribution zip file.   

Q: I don't understand how to implement the Auto FE Updater in a Citrix/Terminal Server environment.
See the Terminal Server/Citrix implementation page.  If you have any questions please email me.

Q: The users are pinning the Access FE database file to the task bar thus bypassing the Auto FE Updater version checking.   This is in Windows 7 and Windows 2008 Server R2.
See the Settings - FE Started by User? page.

Q: I'm suddenly no longer seeing all the options:   (New, Update, Validate, Run, Lockout, etc). It still works, but it only has “Run Config File.”
Q: I moved the Auto FE Updater folder from another system and ....
You are now seeing the same screen the users would see if they clicked on the exe file directly.   Your work station name and network user id are stored in the AutoFEUpdater.ini configuration settings file.    This file can be found in the same folder as the startmdb.exe and contains Master1, 2, and 3 entries.  Only workstations and user ids present in those entries are allowed access to all the options. 
1) The best solution is to open the AutoFEUpdater.ini configuration settings file with Notepad and replace the workstation name with your current workstation name.  This will preserve other settings in the file such as your license key number.
2) The quickest solution is to delete the AutoFEUpdater.ini file and click on the StartMDB.exe so it will recreate the file with your current workstation name in it.  However you will lose a number of other settings in that file.

Q: Where does the shortcut, .LNK file, reside? The configuration file(s)?  And startmdb.exe?
A: These files should reside in a directory on the server, likely called Auto FE Updater.  They should be be in the same directory as the Auto FE Updater utility but that's not a requirement.   While you can have other files in the Auto FE Updater folder I wouldn't recommend it.

Q: Where do the FE file reside on the server that will be copied down to the workstations?
A: The FE Access database file()s (MDB, MDE, ACCDB, ACCDE, ACCDR, ADP or ADE) must reside in it's own  folder on the server.  Along with any other files you want to copy down to the client in the same folder such as add-in MDEs or the Leban's PDF DLLs. 

Q: I'm a bit confused about the directory structure required.
A: You require a directory on the server which is exclusively for the use of the Access front end (FE) database file which is to be copied to the client directory whenever it's updated.   As well as any other files required such as MDE add-ins or DLL files.   All files in this directory will be copied to the client workstation.    This is the MDB/MDE/ACCDB/etc which you update on your own system and then copy up to the server when you complete a feature or bug fix.

The shortcut (which has a .LNK extension although you never see that), Auto FE Updater configuration files and startmdb.exe as well as the backend can be placed in any other directory you desire.  This directory can contain any other files you want.   However I'd suggest you dedicate a directory to the Auto FE Updater and it's associated files.

Q: Can the Auto FE Updater also be used on a front end.mdb (instead of mde)?
A: Yes, the Auto FE Updater can be used with any files.  ADPs, ADEs, Word or Excel files, VB or C++ .exes, etc.  All that matters is if a file(s) is placed in the FE directory on the server with a different date, or a new file, then it gets copied down automatically the next time the user runs the shortcut.

One person uses the utility to distribute an Excel Add-In to a few other users in his company.  But as he seldom does any updates to it he chose to not create any shortcuts.   He also uses the Create User Setup Email to let the other users know when there is an update.

Q: On the server that I use the variable called %username% instead. Is that version related or a choice of the administrator?
A: I get the user name using an API call. I chose to use variable names surrounded by %s in the INI that were the same as the command prompt variables just for some consistency.

Q: It's not creating shortcuts. 
       or
I'm getting the message "1030 - Shortcut creation was not successful for unknown reasons.:"
A: 1) Can you create shortcuts on your or the users desktop manually by right clicking? Some IT departments restrict this capability.
2) You can now create shortcuts in the users My Documents folder.  Not the best option but if the IT department has restricted this what choice do you have?

Q: Where do I indicate the location of my security file?
You need to specify the location of the workgroup file in the Command Line entry just as you would when creating a shortcut.

For example /wrkgrp \\server\share\workgroup.mdw

If you are using the Start Method=Autoselect you will also want to use the MDWFile option as well so the Auto FE Updater knows which version of Access to use to open the client FE MDB/MDE.  You can avoid this by using a different Start Method other than Low Macro Security.

I'm getting the message "Jet 3033 - You do not have the necessary permissions to the MDB/MDE.  This is likely due to the MDB/MDE being secured.  You must then specify the MDW file path and name, User and Password in the INI file. "
See the Workgroup File Settings page and fill in the appropriate information.

Q: Is there any way to insert a command into the Auto FE Updater .ini file to tell it to run either a batch file or .exe file before it does anything else?
Yes, although you can only start a .bat, .cmd or exe file. You can't then start an MDB/MDE running using the Auto FE Updater.  The bat, cmd or exe file will then have to start the MDB/MDE/etc   You can use the Executable Start Method option.

Q: The following error message is appearing:
1019 - The following error occurred while attempting to determine the Access/Jet version of the file [path to our front end] (while using DAO Version 3.6)
Jet 3033 - You do not have the necessary permissions to the MDB/MDE.  This is likely due to the MDB/MDE being secured.  You must then specify the MDW file path and name, User and Password in the INI file.
or
Jet 3033 - You do not have the necessary permissions to the MDB/MDE. This is likely due to the MDB/MDE being secured.  You must then specify the Workgroup File settings in the configuration file."
The only time the Auto FE Updater should be giving you the 1019 error is if you are using the Start Method of Auto Select which I don't suggest anyone uses unless they have a very good reason.  Try using the File Extension option instead.

If you do want to use ULS and Start Method of Auto Select you will also need to set the parameters at the Workgroup File settings page.

Q: I'm trying to use an ACCDR file and I'm getting the following message:
Microsoft Access cannot open this file.
This file was converted to runtime mode by changing its file extension to .accdr. This file will open only when Access is in runtime mode.
To open the file, either double-click it in Windows Explorer, open it by using a shortcut or use the /runtime command-line switch.
To modify the design of this database, rename it with an .accdb file name extension, and then open it in Access.
Go to the Command Line screen and add /runtime to the Command Line.  In a future version I will do that automatically if an ACCDR file is found.