Remote Access to MSACCESS

[Guest]

I have a MSaccess Database we use within a small office. We are planning an
expansion with remote users. It seems we have a couple of option.

1. Run Terminal Server and let the remote users login and run the application.
2. Setup a VPN and let the users connect remotely to the data.
3. Do some kinda web thing where the data sits on a WEB server.

Since each require expansion of money and knowledge, I was wondering if
anyone would give some commentary or suggestion on what they would do if they
were in my shoes?

Thanks,

sammie

 

[Albert D.Kallal]

I have a MSaccess Database we use within a small office. We are planning
an
expansion with remote users. It seems we have a couple of option.

1. Run Terminal Server and let the remote users login and run the
application.

If you have windows server 2000, or later, you can actually run two remote
users for free. (you do have to run them in admin mode). So, often, this is
a zero cost approach.

If you don't have windows sever, then I suppose you could users login to
their existing computers *if* it was a case of a employee wanting to work at
home, and you correctly setup the connection.

2. Setup a VPN and let the users connect remotely to the data.

You can't do the above, due to reasons of speed. I explain in detail here
why you can't use a vpn.

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

however, you certainly are encouraged to setup a secure VPN between the two
locations, and use option #1 (so, TS will well work if you setup a VPN).

3. Do some kinda web thing where the data sits on a WEB server.

Well, sure, but that means you have to setup a web server. (and, you likely
don't want to expose that web server and your network to the wild internet).

Since each require expansion of money and knowledge, I was wondering if
anyone would give some commentary or suggestion on what they would do if
they
were in my shoes?

TS (option #1) is likely the best option. From both a cost point of view,
and the fact that no changes need be made to existing software is likely the
best approach.

Another option not mentioned, is to keep the front end as ms-access, but
move the back end data to sql server, as once again that can be used over a
WAN.

In addition to the above article on WANS', You might as well read my article
on why you split a database. This article also explains why a break in a
connection such as a VPN over the net can damage a mdb file share.

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm