FE / BE

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Meredith McGowan - 01 Mar 2005 18:55 GMT

I just learned today that I need to have a front end and back end on my
database. Therefore, I need some help understanding how this works. I
have created the split and have a backend on the server. What exactly is
the front end - i'm assuming it is the database I created my backend from?
How do I put a personal FE copy on the computer of each user? or should
they all access a single copy of the FE from the server? Will the BE
update the FE so that each user has the most current info? I also read
something about compacting the back end? Any information, comments,
thoughts, suggestions would be helpful.

Reply to this Message

Rick Brandt - 01 Mar 2005 19:08 GMT

Meredith McGowan via AccessMonster.com wrote:

> I just learned today that I need to have a front end and back end on
> my database. Therefore, I need some help understanding how this
> works. I have created the split and have a backend on the server.
> What exactly is the front end - i'm assuming it is the database I
> created my backend from?

A split Access app is where one file has nothing but tables and another file
has everything else. If you used the splitter wizard you should have one
file with only tables (that is your back end) and one file that has all your
forms, reports, queries, etc. (that is your front end).

> How do I put a personal FE copy on the
> computer of each user?

Copy it to each of their hard drives. Batch files or other automatic methods
can be used to update everyone's front end file when you make changes. Tony
Toews has a free utility for this, but if the front end is not too large you
can simply replace the copy every time it is used with a batch file.

> or should they all access a single copy of
> the FE from the server?

NOT recommended.

> Will the BE update the FE so that each user
> has the most current info?

Backwards. The front ends contain links to the tables in the back end so it
is the front end that is applying changes to the back end which all other
front end files will "see".

> I also read something about compacting
> the back end?

If you're not doing a lot of deletions it might not be necessary except once
in a while to clean up indexes and such. Not easy to automate because it
can only be done when all users are out of the application.

Signature

I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Reply to this Message

Douglas J. Steele - 01 Mar 2005 23:31 GMT

In addition to the good advice Rick gave you, you might be interested in
reading what Tony Toews has to say on this topic at
http://www.granite.ab.ca/access/splitapp/index.htm

You might also be interested in the free Auto FE Updater he has at
http://www.granite.ab.ca/access/autofe.htm

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

"Meredith McGowan via AccessMonster.com" <forum@AccessMonster.com> wrote in
message news:ff1c2510987447d7a3e7b8a221c6c3ce@AccessMonster.com...

>I just learned today that I need to have a front end and back end on my
> database. Therefore, I need some help understanding how this works. I
[quoted text clipped - 5 lines]
> something about compacting the back end? Any information, comments,
> thoughts, suggestions would be helpful.

Reply to this Message

Larry Linson - 02 Mar 2005 22:36 GMT

"Meredith McGowan" wrote

> Therefore, I need some help understanding
> how this works.

You'll find a PowerPoint presentation giving an overview of Access in a
Multiuser Environment at http://appdevissues.tripod.com. You may find
something useful, also, on "versioning" in the articles at
http://accdevel.tripod.com.

Doug has already give you a link to MVP Tony Toews' site which has the best
detailed information and links on multiuser Access that I have found.

Larry Linson
Microsoft Access MVP

Reply to this Message