Database splitting

  • Thread starter Thread starter jackalope
  • Start date Start date
J

jackalope

I've read of the advantages to splitting a database into a
front end and back end, with the data being stored on the
network and the forms, etc. stored on the client PCs.
However, in our case we have a database that is used by
only 3 users, two of whom are secretaries with neither the
knowledge nor the time to make their own forms, reports,
etc. If there is a specific report they need, they ask me
to do it for them, which is part of my job.

Given that, is there any advantage to splitting the
database? If so, is there any problem with putting the
two "ends" on the server but in separate places? That way
I can make updates to the structure that is automatically
available to all three of us. Any thoughts on this?
 
Tony Toews has a bunch of information at
http://www.granite.ab.ca/access/splitapp/

In a nutshell, I wouldn't think of not splitting, even for a single user
application. The first time you need to change a form or report, you'll see
why!

You really want only the backend (the tables) on the server: each user
should have his/her own copy of the frontend, preferably on their hard
drive, to minimize the chance of corruption.

If you're concerned about all users having the latest and greatest version
of the front end, Tony's got a free Auto FE Updater at
http://www.granite.ab.ca/access/autofe.htm
 
Just a testimonial. I tried to run a DBase for my school to track and report students who were tardy on 1 database. Not everyone is... how should I PC - it... technologically proficient. I wrote directions for people to copy the shortcut to their desktop and they took the actual database instead. I was constantly looking for the database on machines around my school.

Now, I have a backend somewhere else and the frontend where the teachers can see it. They get confused and move the frontend from the server to their desktop occassionally, but, now I just restore the frontend to the server and I don't have to worry about it

Splitting the dbase may seem like a pain right now, but it is worth it. Believe me

RI

----- Douglas J. Steele wrote: ----

Tony Toews has a bunch of information a
http://www.granite.ab.ca/access/splitapp

In a nutshell, I wouldn't think of not splitting, even for a single use
application. The first time you need to change a form or report, you'll se
why

You really want only the backend (the tables) on the server: each use
should have his/her own copy of the frontend, preferably on their har
drive, to minimize the chance of corruption

If you're concerned about all users having the latest and greatest versio
of the front end, Tony's got a free Auto FE Updater a
http://www.granite.ab.ca/access/autofe.ht

-
Doug Steele, Microsoft Access MV
http://I.Am/DougSteel
(No private e-mails, please
 
thanks to both for the input. I'll give it a try on a
copy of the database (it's not very large) to make sure I
know what I'm doing before I try it on the real thing.
 
Back
Top