Connecting to SQL via Internet

[AkAlan]

I am trying to migtate an ACCESS 2k database from a front end/back end setup
to using a SQL Server for the back end. I will have the SQL Server running on
a MS 2003 Server which will be accessible for the front end users via the
internet only. My IT guy tells me there are two opyions and I would like
advice from those who have had experience with this situation.

Option 1. The users all connect using a VPN connection with a copy of the
Access Project front end on their desktop. Upside seems to be that user
connection is relatively transparent but every change to the front end means
I have to distribute the front end to each of the users.

Option 2. All users connect using Remote Desktop Connection and run the
frontend from the server. Seems like this would work better for changes to
the front end since I would only have to make updates to one place but I'm
concerned with the number of simoultaneous users. I don't expect more than
about 10 users to be using the front end at any one time.

Any suggestions even if they are different would be great. Thanks in advance.

 

[Albert D.Kallal]

Well, remote desktop is certainly a nice way from a admin point of view.

As for the mdb part, you can certainly keep it as a mdb, and link to sql
server tables.

However I suspect the best performance will be that of using remote desktop.

The only issues of remote desktop is licensing can be quite expensive, and
with sol server, you got a good number of free database systems from MS that
you can use. So, sql server with a mdb (or, if you wish adp) front end is
likely much cheaper then remote desktop. On the other hand, if you got the
licensing in place, then likely remote desktop is the way to go (since then,
the end users don't even have to have ms-access installed).

I would vote for remote desktop if you got it in place, since then with only
10 users you likely could run a split database, and not need sql server at
all.

However, as mentioned, there is several sql server engines that are free
from ms, and thus a split mdb to sql server is likely cheaper. (or, as
mentioned a adp if you are going to use adp's. - for existing applications,
you likely will find it much easier to use a mdb, and link tables to sql
server).

I explain some choices you have here:

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

You don't mention the total number of uses you have now on the lan, but if
the total number is small, then you might not need sql server at all here.

 

[aaron.kempf]

what you SHOULD do for remote databases

is use ACCESS DATA PROJECTS
they handle extremely well for some situations