[AccessD] Fwd: Backend Database corruption using VPN access

[Jim Dettman]

Mark,

  #3 is a no-no.

  Quick way out as the others had said is an RDS setup.   Basically plug and
play, although your app might need adjustments.   With an RDP server,
everyone will have the same C:\ drive, so things like creating temp
files/tables might be an issue.

  Also, it doesn't negate the need for everyone to have a separate copy of
the front end.  The way to handle that is to map a drive letter in their
profile (I use X:\) with:

 C:\TSDrive\%Account name%

 They execute via X:\  so each user is pointed to their own copy.

 While converting to SQL would help, your remote users over the VPN would
not be happy.   In general, most that convert to SQL see a performance
boost, but that's not always the case.   Sometimes you need to make
extensive changes to your app in using pass-through, views, stored
procedures, and triggers to get good performance over a WAN.

  You also should have an entirely different mindset in developing the app.
For example, with a true client/server app, you would never dream of binding
an entire table to a form and letting the user browse records like this.

  There are some tricks though, which are pointed out here:

https://www.jstreettech.com/downloads.aspx

 in the download "Best of both worlds", which would get you by most likely.

Jim.

-----Original Message-----
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








		
	


Gang - 
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
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com