Re: Best Practice for Sharing Access on the internet
Firstly, I found the CAL's Client Access Licenses to be affordable so I was quite happy with Terminal Services. I believe that there is an issue with MS Exchange and Outlook Clients being on the same server. You can use Web Mail but I don't know if you can integrate TS with the main Windows Server.
This is a simplistic overview. Having installed the Terminal Server, it is like multiple installations of PCs but on one box. You load Office once and the Cals take care of the licencing issues. There may need to a decent amount of RAM and reasonable upspeed on the Server side.
Mapped the directories to the existing Windows Server as I would any PC.
I created user accounts and separate and Database directories for each user. Loaded an mde or accde FE looking at the back end to one of the mapped directories. As Galaxiom pointed out the database calls are local so there is less opportunity for data corruption through connection outages.
Mapped documents and images to the relevant mapped directories.
Loaded any local printer drivers. Allowed the remote users to use their own printers - Default Printer.
Set-up Outlook for each user.
VPN does allow roaming, licences maybe required so user can access, protected, via the VPN the Terminal Server. Can be a bit slow in some place but I managed to update system from NZ.
It is more Technical than this and you may need techinical assistance to begin with.
I have developed site using ASP Classic and ASP.net and I would still go for the Terminal Server solution. Yes it does cost and it involves an investment - is it worth it to your company.