FE/BE questions

[Kevin]

I am considering splitting a database to be a FE/BE structure, but want to
make sure it results in allowing me to reach my goal.

My goal is: I want to have the ability to modify queries, forms, reports,
etc. without having to "kick" all users off of the database so I have
exclusive access.

My question is: If the Front End is on each users local hard drives, when I
make modifications, do I have to update every user's local .mdb?...or do I
modify in just one location and they are all automatically updated with the
modifications?

I also have a second question. I have reviewed a number of posts in regards
to this topic. Some say it improves database performance, some say it can
get worse. What criteria would/could determine this?
Thanks in advance for feedback!

 

[Rick Brandt]

I am considering splitting a database to be a FE/BE structure, but
want to make sure it results in allowing me to reach my goal.

My goal is: I want to have the ability to modify queries, forms,
reports, etc. without having to "kick" all users off of the database
so I have exclusive access.

My question is: If the Front End is on each users local hard drives,
when I make modifications, do I have to update every user's local
.mdb?...
Yep.

or do I modify in just one location and they are all
automatically updated with the modifications?

There are methods you can create to automate the distribution of new front
ends. Tony Toews offers a free utility that does exaclty that.

I also have a second question. I have reviewed a number of posts in
regards to this topic. Some say it improves database performance,
some say it can get worse. What criteria would/could determine this?
Thanks in advance for feedback!

It depends. Bottom line is that there are so many advantages to splitting
that even if performance is worse in any particular situation you should
still do it.