Deploy of front end

[Cameron Evenson]

Hello.

I am apps support for a application written in Access that is distributed to
various divisions within the company I work for. For the most part when
releasing a new build of the front end I would have to re-link the backend
to it at the sites. What I would like to do is write the front end to
understand that the tables are always in a specific location and re-link the
back end data upon opening of the application. But what complicates this
whole process is that there is also specific security by way of a security
file for each location also. Is there a way to build a mde file so it is
pretty much generic and that when placed in the correct folder for the front
end that it locates the security file and than with coding also locates the
backend files when it first opens?

If this is possible, how would I go about doing that? Examples would be
nice.

 

[Peter Hibbs]

This code may do what you want.

Go to :-
http://www.rogersaccesslibrary.com/index.htm and then click on Other
Developers Libraries, look for BE ReLink.mdb under Hibbs PeterS.

HTH

Peter Hibbs.

 

[Klatuu]

Assuming all your users will be linking to the same back end, the proper way
to deploy an Access front end is to use UNC paths rather than drive letter
paths. You can't be certain that all users will have the same drives mapped.
So rather than

T:\AccessApps\app_be

Use

\\ServerName\AccessApps\app_be

Here is a link to an API that you can use to translate you drive lettters to
the UNC path:

http://www.mvps.org/access/api/api0003.htm