A client’s employees have been working from home since March. They use several custom Microsoft Access applications on a daily basis. Those applications are split-architecture (local copy of frontend MDE/shared copy of backend MDB).
Currently, a user does the following:
1. From their home PC, they connect to the company VDI platform.
2. From the VDI platform, they take remote control of their onsite PC.
3. By remote control, they log into frontends that reside on the onsite PC.
Frontends on the onsite PC connect, via LAN, to backends (in a fileshare) on a dedicated, onsite PC. This seems to work well. In this scheme, they (essentially) are working onsite, but using really, really long monitor/keyboard/mouse cords that stretch all the way to their home.
Some other employees have only company laptops, which they use from home. They VPN into the company, but have no onsite PC to remotely control.
Because they have access to the onsite fileshare, via VPN, it is possible for them to log into copies of frontends on their laptops at home, which would connect, via VPN rather than LAN, to backends in the onsite fileshare.
I am under the impression, however, that connecting to a shared Microsoft Access backend via anything but LAN is inherently unstable, and this proposed laptop scheme could lead to crashed/corrupted backends.
What experience, insights, or links can experts here share to address this concern, one way or the other?