front-end or back-end

[W]

Hi,

What is the use of front-end (FE) and back-end (BE) in Access?
I work on a server, where I store the database.
This allows me of course of changing my forms, queries , reports or modules
only in one place.
Is there any advantage in using tfe FE/BE approach in Access?
Are there any good books about this approach ?

Thanks,

W

 

[NetworkTrade]

if you are single user than there is no need to split

if it is multi user then one splits fe/be so that all can work
simultaneously on separate fes

one can modify one fe without kicking off other users from their fe......

 

[John W. Vinson]

Hi,

What is the use of front-end (FE) and back-end (BE) in Access?
I work on a server, where I store the database.
This allows me of course of changing my forms, queries , reports or modules
only in one place.
Is there any advantage in using tfe FE/BE approach in Access?
Are there any good books about this approach ?

See Tony Toews' excellent discussion at

http://www.granite.ab.ca/access/splitapp.htm

The highly esteemed _Access <version> Developer's Handbook_ by Getz, et al.
has an extensive discussion if you want something you can peruse offline.

John W. Vinson [MVP]

 

[Douglas J. Steele]

Even for single user databases there are advantages to splitting.

If you want the database on the server so that it benefits from regular
backups, you should still have the front-end on the user's desktop to reduce
the amount of network traffic.

If you want to be able to make changes to the functionality of the
application, you should have it split so that you can simply replace the
front-end without impacting data already entered.