Chewy,
You may want to research a bit more on SQL Server...its not something where you can just slap on and start developing full blown apps. You have to deal with security issues, authentication, triggers, stored procedures, views, as well as many more things that creep up.
Basically right now you create an mdb and have full
access to tables, queries, forms, modules, etc. With SQL
server you're basically working with a back end tool
where you deal with tables, views, sproc's, security, etc...
everything but GUI. You then need a front end to physically
connect to a database. See with access you don't need
to provide any sort of connection string to access the database
you have the tables there for you. With SQL Server you
design a front end application which does a lot of talking
to your SQL Server back end. Your back end has to deal
with constant calls to re-open or close the db over and over.
SQL Server is no where near as easy as access. Usually
corporations will have full blown DB admins as well as db
developers working on your SQL Server...sometimes the
developers get shafted and end up being the admins as well..
lucky us.
I'm surprised you have a full blown copy of SQL Server..its
pretty expensive. In any event if you are working
for a company who uses SQL Server you can have your admin
install client and tools, this will give you access to the
enterprise manager (where you create tables, etc) as
well as some other neat db utility apps. You then have
your admin install BOL which is books online, basically
the SQL Server Bible.
Once this is all installed you need to think about how
are you going to deploy. Will this be ASP (internet) based
will this be client server (C++ / VB) etc. You can then
install whatever tools you will use to create your front end.
Once your ready start reading BOL and discovering how much
more work is involved with SQL Server rather than access.
Life...so simple yet so difficult.
Hope this helps a bit,
Jon