Automate DB Install

speakers_86

Registered User.
Local time
Today, 14:33
Joined
May 17, 2007
Messages
1,919
Is there a way to automate a db install on a networked office, so that about anyone can do it? Im talking about splitting, placing be on server, placing fe on computer (and another folder of graphics), and setting trusted locations so the fe works, setting the db icon for the fe (forms/reports)?
 
I found this to be the easiest way.

If you look here, you will find what you need:
Auto FE Updater

It is very simple. Just run the EXE from the server and it does the rest. Now the user can use the desktop short cut. When the start the EXE from the server using the desktop shortcut, it will automatically copy any update to the local PC and then launch the front end.
*** You can use this without making any changes to your database!

You might also want to check out Bob's version:
FRONT-END AUTO-UPDATE ENABLING TOOL
 
Last edited:
Splitting is a design job not an installation task. Supply FE and BE separately.

Distributing the FE can be done with an excellent free tool called Auto FE Updater. http://www.granite.ab.ca/access/autofe.htm

It can also automatically install any other files you want and sets the icon. All the end users need is a shortcut. If the source files change they are distributed when the user runs the shortcut.

Trusted locations can be set up by running a reg file. However in a properly configured network the ordinary users should not be able to run regedit. Run it as a Group policy script.

Installs can be done on the server with a VB or VBA script or even a DOS batch file.
AutoIT is an excellent alternative for automating all kinds of stuff. It has a very useful RunAs function.
http://www.autoitscript.com/autoit3/
http://www.autoitscript.com/autoit3/
This free install packager was posted here recently and looks very interesting.
http://www.jrsoftware.org/isinfo.php
 
This is an interesting question.... what if you were to supply the front end using Access runtime, how could you possibly link the data if you haven't already put the back end on the server????
 
This is an interesting question.... what if you were to supply the front end using Access runtime, how could you possibly link the data if you haven't already put the back end on the server????

The easy way is to use mapped drives.

Even if you don't have another computer available during development you can map the BE on your own computer to the intended drive letter using the SUBST command.
http://www.computerhope.com/substhlp.htm

Link the FE to this mapped path.

Install the BE on the new server.
Map the server BE folder to the same drive letter on the client machines.
The mapping can be done in Group Policy.

Otherwise include a form that allows a suitably empowered user to enter a location for the BE and run the procedure to relink the tables.
 
Seems resonable. This got my curiosity because all of my very few clients either only need a single user or I set up their network also.
However, the "suitably empowered user" part of option two, leaves me with a bad feeling, LOL.
 
Otherwise include a form that allows a suitably empowered user to enter a location for the BE and run the procedure to relink the tables.

What do you think of this as code to relink the tables? It looks to me like that code does it for you, I would just have to make the form that allows the user to select the location of the be.
 
What do you think of this as code to relink the tables? It looks to me like that code does it for you, I would just have to make the form that allows the user to select the location of the be.
I have used this code and it seems to work very well.
 
One point of contention of allowing a user to install their own app from the server. Many of the larger companies I've worked for won't allow the pC user admin rights to install anything and in most cases requires IT involvement. At that point, I usually just provide installation instructions for a DB that has already been split, etc. It just needs to be copied/installed to the local pc.
 
perhaps i'm wrong, but i think installing access apps is never quite as easy as installing an exe file - especially if its not the run time

i suppose most developers here are working with clients, not distributing self installing shrink wrapped products.
 

Users who are viewing this thread

Back
Top Bottom