Running MS Access over VPN
We have an Access database that runs ok on a Windows Server, but we have significant performance issues when attempting to use the database when working from home over our VPN via Cisco AnyConnect. Since we all have laptops, and bring them home when working from home, there is no PC in the office to use RDP.
How do people normally get good performance when running MS Access remotely if they aren't using RDP?
How do people normally get good performance when running MS Access remotely if they aren't using RDP?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A small demo some time ago ...more than 100 columns.. (error in the description)
1000 rows...
ADSL line around 14 mbps
Ping 50 ms
VPS hosting ...MySql ServerIntel(R) Xeon(R) CPU L5640 @ 2.27GHz, 1 cores, 1 GB
https://www.linkedin.com/in/tsgiannis/detail/recent-activity/shares/
1000 rows...
ADSL line around 14 mbps
Ping 50 ms
VPS hosting ...MySql ServerIntel(R) Xeon(R) CPU L5640 @ 2.27GHz, 1 cores, 1 GB
https://www.linkedin.com/in/tsgiannis/detail/recent-activity/shares/
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry for the delay. Thanks for all of this valuable input. I suppose our options are
1. Leave a machine on in the office that one person at a time can connect to RDP and open the database on the local machine from a remote PC, or
2. Migrate to Sql Server back-end and make sure all of our queries are tuned to run server side.
Thanks very much to all
1. Leave a machine on in the office that one person at a time can connect to RDP and open the database on the local machine from a remote PC, or
2. Migrate to Sql Server back-end and make sure all of our queries are tuned to run server side.
Thanks very much to all
One of my clients has a bespoke line of business application developed and deployed in Access that is used across three different offices plus a dozen remote users. The data and all the intensive data managment parts are in a SQL Server database; the Access side consists of many forms with code and reports, with a few dozen local queries that support subform data displays or reporting.
The SQL server is a on a virtual machine on a Hyper-V server. A different server has the corporate shared files. The current version of the application is loaded to the end users when they log in via group policy (which is managed on a 3rd server that houses the domain Active Directory). One of the office locations has the servers and all three have Cisco ASA routers connected to fiber-optic based 300mpbs/300mpbs internet service. The routers create a private WAN so as far as each office is concerned they are all on one network.
Remote users connect to the network with Cisco's AnyConnect and generally speaking they use the application without issue. None have internet at home that is less than 100mpbs/25mpbs.
Lastly, only about 15 users have a need to connect with this application, and I doubt there are ever more than 10 in at one time, typically only about 5. And only 3 or 4 of those users ever have cause to click a button that fires one of the complex stored procedures that runs for more than a few seconds (some run for minutes).
So it's do-able ... but you really need to focus on splitting the data and front end, and without serious internet service and hardware you invite problems.
The SQL server is a on a virtual machine on a Hyper-V server. A different server has the corporate shared files. The current version of the application is loaded to the end users when they log in via group policy (which is managed on a 3rd server that houses the domain Active Directory). One of the office locations has the servers and all three have Cisco ASA routers connected to fiber-optic based 300mpbs/300mpbs internet service. The routers create a private WAN so as far as each office is concerned they are all on one network.
Remote users connect to the network with Cisco's AnyConnect and generally speaking they use the application without issue. None have internet at home that is less than 100mpbs/25mpbs.
Lastly, only about 15 users have a need to connect with this application, and I doubt there are ever more than 10 in at one time, typically only about 5. And only 3 or 4 of those users ever have cause to click a button that fires one of the complex stored procedures that runs for more than a few seconds (some run for minutes).
So it's do-able ... but you really need to focus on splitting the data and front end, and without serious internet service and hardware you invite problems.
Most of my clients that require remote access to an Access application, use Citrix that they run themselves. That allows them to have both local LAN users and remote Citrix users. If your client can't host Citrix themselves, then ALL users must connect via Citrix, there cannot be a mix. Remote Desktop also works very similarly to Citrix but your setup seems to not support multiple users. I never set up a Remote Desktop operation but you should probably talk to an expert. All I can tell you is that it can support multiple users and does not require a VPN.
You need to turn towards RDP, TeamViewer, Terminal Services, CITRIX, ...