Splitting a Database - Best method for distribution of FE

[Evelyn]

I am a contractor working with Access databases created by those who came before me. I have a shared database on the network, that is being simultaneously accessed by multiple users, which I would like to split.

I have split databases before with a few users, and have gone around the office pasting the FE to their desktops and updating the linked tables. However, in this case there are multiple users in various locations that access the database.

I was wondering what the best method is for distributing the front end for a split database, knowing that as the database continues to be updated/developed, these will be replaced.

Any "best practice" ideas are very appreciated.

Thank you in advance.

[zmbd]

One thing that many of us have done is use a Batch-File (think MSDOS days) that copies the front end from the network to the local drive.
Send a link out to the batch file to the user and have them run that file instead of the front-end.

In this case, the Front-end sits on the network and the tables are linked to the back-end from that location using the UNC path name (\\server\path...\backenddata.addb); thus, when copied to the local drive the backend does not need to be relinked.

I also have code in my front-ends that allows the user to locate the back-end and relink should something fail to keep link.

There are several such scripts to be found by your favorite search engine.

There are many other methods... most of my front-ends are small enough that I simply email them in-house to the users after establishing the UNC path to the backend in the table links.

[jforbes]

Here are an Article that may be worth reading for you:
Working with Front and Back-Ends

The second post takes you to the Bytes Question that has the Script I use. If you would rather have the script posted here, let me know.

[NeoPa]

Hi Evelyn.

This article (Front-End / Back-End (FE/BE)) discusses the process of splitting a database.

The simplest approach to distributing it is to have a master copy held at a known location on the network and give the users shortcuts to a script file (.CMD) which will copy this file over their own local copy. The CMD (or BAT for the dinosaurs) file can be the same for each user if the shortcut causes it to be run from the folder where the destination FE is located. Quite straightforward, and we can even help with that if required.

[zmbd]

jforbes - I forgot about that insight article... good catch!

[Evelyn]

You all are SO AWESOME!!! Thank you so very much for all the help!! I appreciate it so very much!

[NeoPa]

I won't argue with that Evelyn. These boys are some really reliable Access experts.

BTW. Belated congratulations to both of you on reaching a thousand and five thousand posts. All pretty high quality to boot.

[jforbes]

Glad to help, Z.

Thanks Neopa, it makes me feel really good.