I work from home, where I can access the VPN, and would like to
send new front ends to the users easily and work on the back end remotely.

You can't use split database over most VPN's. So, while you can "send" new
updates to your system via a VPN, you can NOT run a split database across a
VPN. If you can't get up to speed on these technologies, then you might
consider hiring some consulting help, as you really don't want to make a
mess here, and venturing into something that you don't have the correct
skill sets here (why put your reputation, and even your job at risk?).

Anyway, so save you some grief, you can read the following about ms-access
and deploying ms-access on a WAN or vpn:

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

Should I stay
with Jet or use ADP?

Hum, the above again, the hints at some confusing here. JET, and ADP are not
interchangeable. JET is a database. ADP is a particular type of ms-access
file that works with sql server. Note that you can use a mdb, and link the
tables to sql server (most of us developers prefer this approach over that
of a ADP - but, a good deal of explain is needed to decide which is a better
choice for a given situation). ADP's are more tighelty integrated with sql
server. One main advantage of a ADP is that the ADP includes tools to create
tables and users on sql sserver. So, a ADP is better for inexpainced users,
as writing poor quieres etc. will NOT slow down the speed of the
application, and you don't need to use the server side tools at first. So,
for some, if they are gooing to use sql server, then ADP is a possbile
choice. If you use a mdb, and link tables to sql-server, then you need to
use extra caution in buidling the sql. Fruther, you will also use the
"server side" tools to create the tables when you link a mdb. On the other
hand, even with a ADP since you ARE GOING to be use sql server, then you
likey should, and will have to learn some of the sql srever managment tools
anway. So, why not learn those tools anway? Furhter, creating a table in
sma-ccess, or creating one in sql server is really very simple thing.
Creating tables repsens a tiny fraction of the develpuemtn cost, so either
approach is not a big deal here at alll. On the other hand, desing of the
tables, and having correct relatonsthios and a normalied desint is the MOST
IPROANT thing to get right!!

Since you GOT to learn some of those tools, then you will by the very nature
of the development process use the server side tools to admin, and work with
the database anyway. The fact that a ADP has some tools to let you create a
table is of a very minor nature, and would NOT be a issue of deciding to
use a ADP project over using a mdb project that is linked to sql server.
So, both a mdb or a ADP can be used with sql server. It is not a either or
choice here.

Would it be better to have the forms on the server too and not worry
about
delivering new forms to each user separately?

The above question requitez that you, (or your devlopers) can understand the
diffence betwene an appcliaton, and a file. Often, people using ms-access do
not take time to learn the diffence between what is a file, and what is a
applation. To grasp this simple, but often overlooked convovpet, you can
read the follwing about using ms-access in a multi-user envoment.

http://www.members.shaw.ca/AlbertKal...plit/index.htm

You are going to be working with a good number of technologies here (sql
sever, ms-access, networking etc), and you might want to enlist some help at
the start of this project, as you want to get this right. A good source can
be other departments, or even students (for example, if you have a bunch of
students taking some courses where they learn sql server, then these people
can help you you to use, and setup sql server).

Finally, if you want to use wireless technologies, pda's, tablets etc, then
you likely need to bring in some consulting help. Each of the mentioned
disciplines such as ms-access, sql server, wireless technology, pda's etc
can take YEARS of learning for EACH discipline. In fact, you can spend 6
years just learning ms-access, and you will not near have mastered the
product (that is as long as most degrees that your institution offers! So,
while you could let first year students do some brain surgery...it is not a
very prudent approach...and you need to consider the same for ms-access).


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.members.shaw.ca/AlbertKallal