Ok, Here is a question for you all.
I used to make a lot of MS Access databases for my clients. I later upgraded them to SQL Server backends with the same MS Access front-end. Then I moved onto Access Data Projects, which is specifically made to work with SQL Server. Now, I've been upgrading them all to ASP front-ends within their networks.
So, here comes the networking question:
My clients all see the web interface and want to login from home. Easy, I started off using either a VPN or an open port, which ever they were most confortable with. Now, however, I've got a client who has an MS Access database and I need to make it availabe on the interent. They don't, however, have a full time, static, connection to the internet.
What I would like to do is move their backend to a SQL Server at my server farm. I'd like them to open up their access database as if nothing changed. The apsolutley easiest solution is to open port 1433 on the public server and ... ta da ... I am connected.
But. When I first learned this I didn't realize how utterly moronic that was. I was hacked so fast it wsa just insane.
I can get a router that would only allow a specific ip to access that port (I think), but since they don't even have a static ip, I'd like to use either a domain name (I can give them an app that keeps their dns updated) or a mac id.
so. Anyone. Perhaps another idea.
I've also got a tight budget, so I can't go crazy here.