How to update front-end for MS Access 2007 -
i able split database , used packaging solution distribute front-end. tested exe file , worked fine. updating forms , cannot figure out way of updating front-end (backend on server) wihtout going through new installation of new package. did create template file while going through process of packaging database.
i found website afraid unzip file. have of use tool? http://www.btabdevelopment.com/ts/freetools thank you
some existing tools
here list of deployment tools access front ends:
- auto fe updater tony toews (probably best, commercial)
- application starter peter's software
- front end updater utility, roger's access library
- autoupdater, utteraccess archives
the 1 listed help.
more information on deployment
the issue there no single way update access application.
discovered, packaging tools nice, don't take care of important, , complex, part of deploying software: how update existing installation?
access doesn't have story here, there many custom solutions, each flaws , advantages.
you right in case, must separate backend database, containing tables, front-end, containing code, forms , reports. front-end must deployed each user: rule being front-end meant used single user only.
what's in updater
so, characteristics want in update story:
user should not have anything: want user new version of front-end made available, automatically.
mean front-end check if there new version available on remote folder before allows user login or star work.
if version available, fetched , deployed.sometimes, because development environment may different user's environment (different server names, different shared folders, etc), may need re-link tables in front-end correct path of back-end after deployment.
what using deployments
for few years now, have perfected own system works without stitch.
instead of launching application directly, when user click application icon, small launcher application started.
launcher use simple click-once application (so can auto-update) written in .net.the launcher responsible ensuring main application running once, , checking , deploying new versions (or downgrading them) when updates made available.
updates packaged zip files contain files necessary new update.
name of file contains version number,myappfe-2013-08-01.zip
sorting list of clients packages name make easy pick up-to-date package.
these front-end packages stored on shared folder on server, instance if backend database in\\myserver\myapp\db
, front-end packages kept in\\myserver\myapp\fe
.when launcher detects new package available, deletes existing folder of front-end on user's machine , unzip new package there instead.
once launcher has finished tasks, launches application frontend.
when application front-end started first time, can more checks re-link tables if point wrong location.
notes
an alternative detecting new package keep small text file on server contain filename of current package.
whenever frontend started check if package name running same package name listed in file. if not, upgrade/downgrade necessary.one of advantages of solution once access runtime installed, users can run in normal user session on machine, without ever requiring administrator rights: click-once launcher doesn't require admin rights , if deploy access front-end under user's
%appdata%
folder, not need elevated rights update front-end @ all.the first time deploy, launcher should responsible registering location of front-end folder trusted location access allows run without vba/macros being disabled.
these set of registry keys can add underhkey_current_user\software\microsoft\office\14.0\access\security\trusted locations\
(the exact registry key depends on version of office , whether on 32 bit or 64 bit system).
Comments
Post a Comment