Immediate email alerts of any problems users encounter with the utility. You will have control over the users as well as logging every error, warning, activity including files copied that happens during the execution of the Auto FE Updater program. Or email me on my contact page and I'll email you every time I send out on update. I really want some feedback. What additional features do you want to see? What problems or irritations are you having?
Please use my contact page to email me Or join the discussion on LinkedIn. After opening the splash screen of the FE, I open a version check form that compares the versions. The recordsource of the form gets version Ids from FE and back end BE , using equality because versions may have alphabetical suffixes. Some users may have customized their version of the FE, and not all users may have the same FE. If the update is critical, you could add another field to the BE table and use that instead of the prompt if needed.
If approved, the FE copies an updater database to the user system, shells to open it and then closes itself. When the Updater opens, it presents another warning and asks if user is sure they want to update. If not, shell to the existing FE. If approved by the Updater, the Updater backs up the current FE and copies the new version to the user system, and shells to open it. This is a major case when it may be necessary to reconnect to BE tables. With this in mind, a very common question in a variety of forums then becomes, how do we deploy a copy of the Front-End to our users and ensure that they always get any updates?
Hi, Thanks for all of your efforts with this great site. Do you know of a way of updating Front End applications via the Web?
Your email address will not be published. Skip to main content. Looking For Assistance or Customizations? This is a very old post and I used the autofeupdater until it stopped working so I wrote one of my own and it has evolved over the last few years into something that I have used with many clients. It's so simple to use and there is no interface. Just an EXE and a very simple config file. Please check it out here.
I can also help with custom solutions if none of the configurations work for your needs. After trying all of the solutions above not exactly these solutions but these are the common suggestions in the Access community , I developed a system entirely within Access using VBA that allows an admin DB to create and publish objects to client DBs without the need for user intervention or management of multiple DB files.
This approach has several benefits: 1. It simplifies the development process by having a dedicated environment admin DB for development and testing totally separate from the client DBs.
Can also allow devs to roll back to previous versions if desired. It could be used as a kind of change management system within Access for developers who want to commit multiple changes to objects and modules and retain past changes.
I will hopefully post the code to GitHub soon, I just have to get clearance from my workplace to release it. I will edit this post to include the link when I have. We have usually kept the Access front ends on network drives, and just put up with the need to compact and repair on a regular basis. You will probably find you need to do that even when they are installed locally, anyway. If you must have it installed locally, there are various tools which will enable you to "push out" software updates, and the guys over on ServerFault would have more information on those.
Assuming such tools aren't available, the only other option I can think of is to write a small loader program that checks the local. MDB against a master copy on the server, and re-copies it across if they are different, before then launching the MDB. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How do I distribute updates to a Access database front end? Ask Question. Asked 11 years, 11 months ago. Active 4 years, 1 month ago.
0コメント