What is the reason for splitting a database?

[Lisa]

I have been having a few problems with a database the past few weeks. I have
about 12 users in this database on a daily basis. I have a table with 11000
records, and an associated table with 23000 records that has an associated
table with 6000 records. I am wondering if the database is getting to big.
Would splitting the database help me in any way. Some of the problems are,
when you click on a button that would normally open a form is giving me a
module not found, or when you click on a dropdown box it locks you out of
chosing something from the dropdown. This forces me to compact and compare.

any help would be greatly appreciated.

 

[Paul Overway]

11000 records is small. The problems you're experiencing are typical when a
database is shared and hasn't been split. So, yes, splitting would
definitely help with the corruption issues.

 

[Lisa]

Paul,

Thanks for your response. One more question, is it a problem to split the
database and have only one front end that all the users utilize or does it
make more sense to have them utilizing each their own front end.

 

[Lisa]

Paul,

Thanks for the response. One more question, does it make more sense to have
each person having their own front end or is it ok that they all utilize the
same front end.

 

[Paul Overway]

It makes more sense to have the user use their own copy of the front end on
their own PC. Otherwise, you'd be causing a lot of unnecessary network
traffic and providing yet another opportunity for corruption.

See http://www.granite.ab.ca/access/splitapp/overview.htm