469,579 Members | 1,063 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Share your developer knowledge by writing an article on Bytes.

Front-End / Back-End (FE/BE)

NeoPa
32,198 Expert Mod 16PB
The concept of FE/BE is to separate the code and control parts of a database solution from the design and storage of the data.
Benefits include :
  1. Releasing new versions of the code / control (FE) can be done without having to manage the porting of the data.
  2. Multiple users are less of an issue if the data is stored in a BE database. It's even possible (many developers prefer this in fact) to release the FE database to each user as a local db.
Creating a FE/BE System from an Existing Database.
  1. We'll start off with the existing database (referred to as {A}) and create two new ones (referred to as {FE} and {BE}).
  2. To create the BE db we can use either of the following two methods :
    1. From {A}.
      • Copy the {A} file as {BE} (using Windows Explorer or similar tool).
      • Open {BE} in Access and delete all objects except the native tables (not the linked ones). This will include QueryDefs, Forms, Reports, Pages, Macros and Modules (as well as all the linked tables of course).
    2. From scratch. A disadvantage is that you will need to add various database properties and settings if you want them.
      • Create a completely new database in Access and save it as {BE}.
      • Use File / Get External Data / Import... from {BE} to import all of the native tables (and the relationships) from {A}.
    3. Now {A} becomes {FE}. I would create a copy at this point rather than simply renaming as you would benefit from a backout plan if things go wrong.
    4. Open {FE} in Access and delete each native table.
    5. Create links to all the tables in {BE} by using File / Get External Data / Link Tables....
      • Link to {BE} and select all the tables.
        NB. Anyone using {FE} will connect to {BE} using these links so the address must be correct for everyone. If {BE} is on the C: drive of the PC that you are doing the work on, do NOT link to it as C: unless you know that everyone will be using it from this PC exclusively. Otherwise anyone trying to use it from elsewhere will have trouble accessing {BE}. If this is the case, consider using a UNC path (\\ServerName\ShareName\...) to {BE} which should work from all networked PCs.
This will leave you with a new system where the FE is split from the BE but it should work the same as before apart from this.
Nov 16 '07 #1
1 10857
NeoPa
32,198 Expert Mod 16PB
This article discusses the how tos and details of doing this process manually.

There is also a standard wizard that will do most of this for you, but read this if you want help understanding the issue, as well as if you want to set it up manually for any reason.
Jan 28 '09 #2

Post your reply

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

Similar topics

36 posts views Thread by Digital Puer | last post: by
7 posts views Thread by Abhishek Saksena | last post: by
6 posts views Thread by eight02645999 | last post: by
3 posts views Thread by M O J O | last post: by
5 posts views Thread by Iain Bishop | last post: by
3 posts views Thread by John | last post: by
5 posts views Thread by Steve | last post: by
2 posts views Thread by =?Utf-8?B?R2lkaQ==?= | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.