Home All Groups Group Topic Archive Search About

Concurrent users - benefits of splitting database

Author
6 Oct 2006 6:26 PM
LittlePhil
Hi All,

Firstly thanks to everyone who participates in this wonderful site - saved me
many  a sleepless night!

Question 1:
Please could someone explain the benefits of splitting a databse into FE and
BE?I have looked through many other threads relating to concurrent use of a
database but can't find an explanation of <why> this helps.

Question 2:
Do i need to worry about concurrent use in the situation described below?

Question 3:
This is my first multi user database, are there any other things i should
know?!

Background:
I'm working on an MDB that is to be used by initially 8 users and want to
ensure that it doesn't fall straight over because of concurrent use problems.
It is a simple database in that we will only ever be adding records. I will
regularly be archiving/deleting old records. Don't expect it to get over 30
meg in size - oh and no two users should ever need to view the same record at
the same time. However the forms are quite complicated and have lots of
associated functions to validate the data entry and automate some fields.

Thanks very much,

Phil

Author
8 Oct 2006 8:05 PM
Graham Mandeno
Hi Phil

The two main benefits are ease of maintenance and avoiding database
corruption.

8 concurrent users is no problem for a well-designed database, but it would
be very unwise not to split it and have a separate front-end for each user.

There is some very good discussion on database splitting on Tony Toews
website here: http://www.granite.ab.ca/access/splitapp/index.htm
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Show quoteHide quote
"LittlePhil" <u27595@uwe> wrote in message news:675ef21345414@uwe...
> Hi All,
>
> Firstly thanks to everyone who participates in this wonderful site - saved
> me
> many  a sleepless night!
>
> Question 1:
> Please could someone explain the benefits of splitting a databse into FE
> and
> BE?I have looked through many other threads relating to concurrent use of
> a
> database but can't find an explanation of <why> this helps.
>
> Question 2:
> Do i need to worry about concurrent use in the situation described below?
>
> Question 3:
> This is my first multi user database, are there any other things i should
> know?!
>
> Background:
> I'm working on an MDB that is to be used by initially 8 users and want to
> ensure that it doesn't fall straight over because of concurrent use
> problems.
> It is a simple database in that we will only ever be adding records. I
> will
> regularly be archiving/deleting old records. Don't expect it to get over
> 30
> meg in size - oh and no two users should ever need to view the same record
> at
> the same time. However the forms are quite complicated and have lots of
> associated functions to validate the data entry and automate some fields.
>
> Thanks very much,
>
> Phil
>
Author
11 Oct 2006 7:28 AM
LittlePhil via AccessMonster.com
Many thanks Graham,

Exactly the information i needed :-)

If anyone else is new to splitting a database then read the link Graham sent -
its not too technical and explains why you should be doing this.

Cheese,

Phil


Graham Mandeno wrote:
Show quoteHide quote
>Hi Phil
>
>The two main benefits are ease of maintenance and avoiding database
>corruption.
>
>8 concurrent users is no problem for a well-designed database, but it would
>be very unwise not to split it and have a separate front-end for each user.
>
>There is some very good discussion on database splitting on Tony Toews
>website here: http://www.granite.ab.ca/access/splitapp/index.htm
>> Hi All,
>>
>[quoted text clipped - 32 lines]
>>
>> Phil