What is the value of using a Front End and a Back End ?

[Ann Checkley]

I inherited a database, partially designed in 1999 by
someone with far more knowledge of ACCESS than me. I would
like to learn a few things about the logic used in the
design, as I try to simplify it for our use. He created a
Front End, which contains all the forms and queries, and a
Back End, which contains 98% of tables. I just want to
understand the purpose/benefit of doing it this way.
Thank you for your time.
Ann

 

[Bruce M. Thompson]

I inherited a database, partially designed in 1999 by

someone with far more knowledge of ACCESS than me. I would
like to learn a few things about the logic used in the
design, as I try to simplify it for our use. He created a
Front End, which contains all the forms and queries, and a
Back End, which contains 98% of tables. I just want to
understand the purpose/benefit of doing it this way.

See the following page at Tony Toews' web site for an explanation of some of the
benefits:

Splitting your Microsoft Access MDB into a front end and back end
http://www.granite.ab.ca/access/splitapp.htm

 

[Ann Checkley]

I appreciate the reference to Tony Toews' explanation. I
read it thoroughly and am left with the thought that this
configuration is best left to those who actually write
code and develop massive databases.
Thank you.

 

[Paul Overway]

It is good advice...even for a novice. Databases usually grow in complexity
over time. So, the sooner you split it, the better. It really is a pain to
get everyone out of a database when you need to make changes. Plus the
potential for corruption is very real and you'll be sorry if it happens.

 

[Bruce M. Thompson]

I appreciate the reference to Tony Toews' explanation. I

read it thoroughly and am left with the thought that this
configuration is best left to those who actually write
code and develop massive databases.

It is best for those who make changes to their application (be it occasional or
frequent changes) and, especially, for those who use their database in a
multi-user environment (I *always* split every database I create unless it is
only a temporary file for testing purposes). The size of the database really has
no bearing on such a decision - only the value of your data does.