By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,045 Members | 1,760 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,045 IT Pros & Developers. It's quick & easy.

Releasing Patches for Custom Access Software

P: 171
I have got an application with both front end and back end in access. I have trouble when I want to release a new version of the software as I have to go to each computer, and paste the front end. I can't upload it on to a server and just have them download and install the updates.

Is there a third party software that does this, or some way it can be acheived.

Feb 25 '09 #1
Share this Question
Share on Google+
3 Replies

Expert 2.5K+
P: 3,532
I guess that depends on why you can't do this! Is it because you can't upload it to the server, and if not, why? Or is it because your end users don't have the skills to download and install the updates?

If it's the former, I don't have a clue! Presumably with a split database you are running the back end on a server.

If it's the latter, Tony Toews has a utility called The Auto FE Updater for doing all of this automatically, without end user interaction:

I've never had the occasion to use it, but it has a very good reputation in the Access community.

Good Luck!

Linq ;0)>
Feb 25 '09 #2

P: 171
Thanks missinglinq, that may be what I am looking for, the reason I am looking for this solution is due to the below listed issues:

Issue 1 :if I want to update or Delete or Add Fields in the back end, I have to do it by remote desktop, because I don't want to mess with the back end. Maybe I am doing it wrong.
Issue 2: I have a form where I have a button to link the backend in with the front end, but it is on a on click event, so I have to go to click the button on atleast one front end (then I can copy and paste and the back end is already linked)
Issue 3: The front end has a data source coming from outlook and each persons location for outlook will be different. So I need to check whether the outlook tables have linked correctly.

If there are better ways to resolve these issues I'm all ears.
Feb 25 '09 #3

P: 64
I'm sure many of us have the same issue. My BE tables are in a protected drive f:. I load the new version of the front end on the same drive. Each user has a dos cmd routine that loads the latest version from the F:\ to the c:\ of the current user and then runs the application.

I call it launchtk.cmd and it looks something like this

xcopy F:\TimeKeeper7\TimeKeeper7.accdr "c:\Program Files\TimeKeeper7\TimeKeeper7.accdr" /y
"c:\program files\timekeeper7\timekeeper7.accdr"

Works for me.

Feb 26 '09 #4

Post your reply

Sign in to post your reply or Sign up for a free account.