What are the disadvantages of using the Front-end and Back-end Da.

  • Thread starter Thread starter Rosemary
  • Start date Start date
Hi Rosemary,

I cannot think of any disadvantageous to using a split architecture. I can
think of all kinds of disadvantageous of running an unsplit application,
including:

* Increased risk of database corruption
* Having to kick all users out, to make any changes
* Conflicts between users with temporary tables (if you use these)
* Conflicts guaranteed to arise if different users have different versions
of Access installed. For example, most users have Access 2003 installed, but
a few users have the newer Access 2007 installed. If a 2003 and a 2007 user
attempt to access an unsplit application at the same time, the second one in
will be read only.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________
 
I need to know what are the negative side of using Front-end and Back-end
database.

Performance may be detectably slower.

OTOH driving a car while wearing seatbelts can be a bit uncomfortable.
 
Rosemary said:
I need to know what are the negative side of using Front-end and Back-end
database.

John is correct. Performance is somewhat slower all the Performance
FAQ explains how to get things back nice and fast.

Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

There are many, many reasons for using a split FE/BE system.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless..

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Back
Top