Access front-end / back-end DB Network Bandwidth

[Joe K.]

I have an Access application that was created with a Access front-end
database that has numerous forms and reports. The Access back-end database
is linked into the front-end database which has 100 tables and which is 300
MB.

Presently the Access front-end and back-end databases sit on a server that
takes
145 ms to pick this server from my desktop. Would this Access front-end
database run quicker if the Access front-end database was on my desktop?

Please help me with this issue.

Thanks,

 

[Ray C]

Absolutely.
As a matter of fact, it is the recommended way of doing things in MS Access,
especially in a multi-user environment. All users should have a copy of the
front-end on their local hard drive. You reduce network traffic doing things
this way. Forms will open faster since they don't have to travel though the
network.

Especially since your db is huge (by Access standards). Of course, keep in
mind that this doesn't make the system completely client-server. The queries
still have to travel the network, but at least you've reduced some traffic.

Hope this helps.

Ray

 

[Jerry Whittle]

In a word: Yes. Especially if multiple people were using the same FE.

Access isn't client/server so all the forms and reports need to travel from
the FE out on the server to your PC. Placing the FE on your PC should improve
things.

 

[Bruno Laurans]

SqcwcsSC SC


Le 28/03/08 20:42, dans (e-mail address removed),

 

[Bruno Laurans]

zeferbrsthbrthbf


Le 28/03/08 20:50, dans (e-mail address removed),

 

[Tom Wickerath]

Hi Joe,

As others have already said, yes, you do want to run the FE local
(especially if this is a shared multiuser application). Here is an article
that you may find helpful:

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Larry Linson]

Especially since your db is huge (by Access standards).

Huge, like beauty, is in the eye of the beholder. For several years, I
worked on an Access 2.0 database that contained approximately 1,000 objects
just in the client application... the production data was kept in an
Informix server DB. We got an accurate object count when we did Y2K
remediation work on it. Oh, the 1,000 object count was after we deleted many
objects that we determined were no longer used.

A number of users here have reported their databases have millions of
records (some just split, multiuser and some client-server). Others have
worried because they were edging close to the 1 GB (in days past) or 2 GB
limit (now) on the size of an Access / Jet / ACCDB file, and had to link to
data in multiple back-end databases.

But, I do suspect that a large majority of Access databases in use today are
smaller than 100 tables and 300MB.

Larry Linson
Microsoft Office Access MVP

 

[Larry Linson]

zeferbrsthbrthbf

Proud of your response, Bruno?