Multiple Users FE/BE

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Molasses26 - 12 Dec 2005 21:05 GMT

Hi!
I have a database on our network drive and there are about 30 users who
have access to it. I have it broken into front-end and back-end databases
but I am noticing some significant performance issues. The back-end is
linked to one ODBC Sybase table that is getting close to 100,000 records in
it and then I have one main Access tables that contain additional information
on each of those records.
Right now all of the users have a link to the same front-end program out
on the server and (depending on their permissions) the program either opens
to the main menu (admins only) or creates a recordset of the items assigned
to the person logged on and opens a worksheet form.
My question is -- would performance be better if I gave each user their
own copy of the front-end to save on their PC or is it okay having them all
it the same front-end on the server? The only time we get any record-locks
is if one of the admins get's on and trys to pull up infomation from everyone
else. But I have noticed that it takes about a minute for the users to open
their worksheet and any time they try to re-sort the data it takes a
significant amount of time as well.
Thanks for any suggestions you can give me!
Dawn

Reply to this Message

SHIPP - 12 Dec 2005 21:05 GMT

Absolutely each user should have their own front-end located on their local
drive. That way you are eliminating all of the network traffic that has to do
with your program. The only thing going back and forth on the network is the
data.

Signature

M. Shipp

> Hi!
> I have a database on our network drive and there are about 30 users who
[quoted text clipped - 16 lines]
> Thanks for any suggestions you can give me!
> Dawn

Reply to this Message

Marshall Barton - 12 Dec 2005 22:39 GMT

> I have a database on our network drive and there are about 30 users who
>have access to it. I have it broken into front-end and back-end databases
[quoted text clipped - 13 lines]
>their worksheet and any time they try to re-sort the data it takes a
>significant amount of time as well.

Opening the front end will definitely be faster if you place
it on each user's front end, but you may not see a dramatic
improvement.

However, since Access does write some information to the
front end file, regardless of what your app is doing, there
is a significant chance of corrupting the one copy on the
server when several people are using it at the same time.

Signature

Marsh
MVP [MS Access]

Reply to this Message