Speed of a network Access database

[Guest]

Hello,

I have a split database on the network drive but is being accessed by users
through the front end database that is also on the network but has a copy is
installed on the local terminals of users. I have noticed that whenever, more
than one user is concurrently accessing their version of the front end
database, the response time becomes disturbing slow.

Please advice on what needs to be done.

Al

 

[tina]

have a look at the following webpage:
http://www.granite.ab.ca/access/performancefaq.htm

hth

 

[Arvin Meyer [MVP]]

Do not share the front-end from the network. Each user needs to run the
front-end from his/her own workstation, linked to the data on the back-end
network. The method you are using now is not only slower, but it invites
corruption.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Arvin Meyer [MVP]]

Do not share the front-end from the network. Each user needs to run the
front-end from his/her own workstation, linked to the data on the back-end
network. The method you are using now is not only slower, but it invites
corruption.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Tony Toews]

Do not share the front-end from the network. Each user needs to run the
front-end from his/her own workstation, linked to the data on the back-end
network. The method you are using now is not only slower, but it invites
corruption.

Minor quibble. While it's not optimal you can sun each users front
end from the server. Mind you each person must have their own copy
of the FE.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews]

Do not share the front-end from the network. Each user needs to run the
front-end from his/her own workstation, linked to the data on the back-end
network. The method you are using now is not only slower, but it invites
corruption.

Minor quibble. While it's not optimal you can sun each users front
end from the server. Mind you each person must have their own copy
of the FE.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Arvin Meyer [MVP]]

Minor quibble. While it's not optimal you can sun each users front
end from the server. Mind you each person must have their own copy
of the FE.

Yep. No quibble at all. The keyword is "share". In fact, running individual
copies from a server is the method of choice for a Terminal Server.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Arvin Meyer [MVP]]

Minor quibble. While it's not optimal you can sun each users front
end from the server. Mind you each person must have their own copy
of the FE.

Yep. No quibble at all. The keyword is "share". In fact, running individual
copies from a server is the method of choice for a Terminal Server.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access