[AccessD] Fwd: Backend Database corruption using VPN access
jbodin at sbor.com
Mon Jul 30 22:57:30 CDT 2018
Mark, Access is not a Client/Server architecture so you will certainly have issues over a VPN. Unfortunate.
SQL Server an option for sure, have to re-write certain parts of your app.
Logmein idea would work, I would not set up 6 physical machines, unless they were extras lying around, rather use virtual machines on a host with enough ram to run your Access app.
Another option I have used is to set up a Remote Desktop Server, licensed for x amount of users, and use the VPN to connect each user to a virtual instance of your app. Then, like LogMeIn, the front-end can live on the virtual desktop or local user's machines, and the back-end can live on the server, all on the same LAN. And RDS, unlike the free version of LogMeIn in Central, can print reports back to the remote user's printer as well as you can copy or access files on the remote user's PC. No need to re-write you app with either logmein or RDS server options.
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Monday, July 30, 2018 9:57 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Fwd: Backend Database corruption using VPN access
I was just wondering if anyone has run into this problem:
1) LAN-based Access 2016 database
2) Remote access for one user via LogMeIn to a connected machine
3) Other remote users are using a VPN to access the application directly from their remote workstations.
Certain UPDATE/INSERT operations are causing the back-end database to become corrupted...
but only when the VPN users are doing the updates.
The Remote access user does not exhibit this problem....nor do the locally connected users.
Does anyone know that if we move the back-end database to SQL Server 2014, hosted on the LAN, that the problem will be resolved ?
Other options are to :
1) host the entire Access application with a remote hosting service.
2) Set-up at least 6 workstations that would be accessed remotely via LogMeIn.
Any and all suggestions greatly appreciated.
AccessD mailing list
AccessD at databaseadvisors.com
More information about the AccessD