Multi User and slow database

[Guest]

I am looking to adress 2 "problems"

I have a database on a network.

The network consists of 3 PC's (no server).

The database is housed on one of these and the other 2 PC's work across the
lan.

The first issue is speed - the database has been operational for about 7
months and has collected 4000+ line entries.

It is noticably slower on searching and opening - is there a way around this?

The second is the fact there are 3 users entering/updating and searching
across the database. Is there a way for access to show new data to the other
users without the need to close and reopen the database?

any info/links would be much appreciated.

TIA

 

[Joseph Meehan]

I am looking to adress 2 "problems"

I have a database on a network.

The network consists of 3 PC's (no server).

The database is housed on one of these and the other 2 PC's work across
the
lan.

The first issue is speed - the database has been operational for about 7
months and has collected 4000+ line entries.

It is noticably slower on searching and opening - is there a way around
this?

The second is the fact there are 3 users entering/updating and searching
across the database. Is there a way for access to show new data to the
other
users without the need to close and reopen the database?

any info/links would be much appreciated.

TIA

Step one. Run a repair and compact. That may help. See the "Tool" -
"Database Utilities" menu.

Step two. Split the database. Have a Back end holding just the data and
front ends for each user (including the one on who's machine it is located)
that has all the forms, reports queries etc. Static data, like tables with
information that does not change should also be included on the Front end
databases on the users machines. The idea is that all the processing is
done on the user's machines and not on the server machine. Check the help
file and see the "Tool" - "Database Utilities" menu. for a wizard to help
you with the split.

Remember to make all changes on a copy of your database to protect the
original until you are sure you have it right.

To see the new data have the users try pressing F5 (refresh).

 

[Guest]

I have looked at splitting the database and have read other peoples topics.


I am a fairly novice access user and am woried about the switchboard
becoming "useless"?

Any helpful hints?

TIA

 

[Joseph Meehan]

I have looked at splitting the database and have read other peoples
topics.


I am a fairly novice access user and am woried about the switchboard
becoming "useless"?

You should not need to worry. It is likely to be fine and if it needs
any adjustment, hey, just come back and ask.

Again remember I said to work on a copy of the original database. Just
use a different name for the copy. When done if all works just use the
copy, if it does not, you just wasted about 30 minutes if you are slow doing
it.

 

[Guest]

Thanks for the tips!

generally if someone tries ANYTHING new on an original database - without
making a backup - they should not be using a PC

Will try the split this afternoon. Fingers crossed!

Again thanks for the help!

 

[Guest]

Just an update:

I have done a compact and repair and split the database.

I then copied the front end to each machines desktop (including the host
machine)

I now get like an arrow infront of the tables? does this mean it's linked ok?

Everything appears to work fine and there is a noticable increase in speed!

Many thanks!!

Thanks for the tips!

generally if someone tries ANYTHING new on an original database - without
making a backup - they should not be using a PC

Will try the split this afternoon. Fingers crossed!

Again thanks for the help!

 

[Joseph Meehan]

Just an update:

I have done a compact and repair and split the database.

I then copied the front end to each machines desktop (including the host
machine)

I now get like an arrow infront of the tables? does this mean it's linked
ok?

Yes. That means they are links.

Everything appears to work fine and there is a noticable increase in
speed!

Glad to hear it.