Reduce latency of split DB

[Stephen sjw_ost]

I have an 8MB backend database that I need multiple users to be able to
access using the frontend from multiple locations ranging from Florida to New
Mexico.
Can anyone suggest the best way to have the frontend connect to the backend
with the least latency and problems? I'm grabbing for straws here and am
looking for advice to improve the operation of my database over my companies
WAN. I'm not very sure of the specifics of the WAN so this makes it a bit
more difficult.

Thanks for any suggestions and/or advice.

 

[Allen Browne]

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

 

[Stefan Hoffmann]

hi Stephen,

I have an 8MB backend database that I need multiple users to be able to
access using the frontend from multiple locations ranging from Florida to New
Mexico.
Can anyone suggest the best way to have the frontend connect to the backend
with the least latency and problems?

Using a Terminal Server is the solution which requires the least changes
for your application.

Another solution is to use a SQL Server back-end. Depending on the WAN
speed/latency you can easily use replication (one SQL Server in the HQ,
SQL Express on the local machines using e.g. a merge replication).


mfG
--> stefan <--

 

[Abbey Normal]

Hi Stephen. I had the same problem on a split db with mulitple users in CO
and NJ and solved it with windows terminal server. A license for each user,
the user logs in via Remote Desktop. Made a major difference.

 

[Abbey Normal]

forgot to add. both the front end and the back end reside on the server they
are logging into.

 

[Guest]

I have an 8MB backend database that I need multiple users to be able to
access using the frontend from multiple locations ranging from Florida to
New
Mexico.
Can anyone suggest the best way to have the frontend connect to the
backend
with the least latency and problems? I'm grabbing for straws here and am
looking for advice to improve the operation of my database over my
companies
WAN. I'm not very sure of the specifics of the WAN so this makes it a bit
more difficult.

Thanks for any suggestions and/or advice.

 

[Paul Shapiro]

I agree with Abbey. Using an Access database over a WAN will never give
reasonable performance, and you greatly increase the risk of database
corruption. Access is intended to be used on a LAN. With Terminal Server,
Access would be running on the LAN and only the keystrokes, mouse movements
and screen display move across the WAN.

 

[Douglas J. Steele]

Unfortunately, Access isn't intended to be used over WANs. Check what Albert
Kallal has at http://members.shaw.ca/AlbertKallal/Wan/Wans.html