Access is very slow over a wireless connection

[timsquires1]

We have a large Access program that is respectable in regards to speed
when used over a wired connection, however, when using a wireless
connection(laptop) it can take over 5 minutes to load a form.

Any ideas why our program would react so slow when used with a wireless
connection and be just fine over a wired connection?

 

[Rick Brandt]

We have a large Access program that is respectable in regards to speed
when used over a wired connection, however, when using a wireless
connection(laptop) it can take over 5 minutes to load a form.

Any ideas why our program would react so slow when used with a
wireless connection and be just fine over a wired connection?

Um...because a wireless connection is a LOT slower than a wired one?

It is generally accepted that a standard Access/Jet app cannot be used over
a WAN at all and is not a good idea over wireless of any kind. The
exception being when remote software like Terminal Server is used.

Some of the newer wireless LANs might give acceptable performance (but still
slower than wired), but you still run a much higher risk of corruption due
to dropped packets. Even on a wired ethernet network Access is very picky
about hardware and performance.

 

[Allen Browne]

Running an Access database over an unstable network connection such as WiFi
is quite a good way to corrupt the database.

If you really need to do this, you might consider running it through
Terminal Server or Citrix, where the session actually runs on the server.

Details:
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html