Richard,
Which tutorial(s) would you recommend based on the following:
We currently have a 2003 database that tracks fitness results at a specific location. Right now it is one database on a standalone pc. Other locations are slowly coming about and we would like to track every record at a centralized location (ex. Fitness results, number of members, etc.), thus we need a web enabled database for the users at the other location to enter information. The idea of using a SQL Server came about because we have strict HIPAA laws. What would we need to do to take a 2003 (un-split at the moment) database to the next level? And with moving to a web based database, would we lose the years worth of work put into the development of forms, reports, etc when migrating to SQL Server?

---

Reply from Richard Rost:

There are a LOT of ways you can do it. You can save your data in an SQL Server database and then just connect to it from the other locations over the Web using Access and ODBC. I've been thinking about putting together a short seminar on how to do this. It's not terribly hard. This would allow you to keep your forms and reports and your data would essentially be in linked tables. The end-user would require the Access front-end though.

You could set up a Sharepoint server and do basically the same thing... although I'm not completely sold on Sharepoint yet.

The BEST solution is to build a web-based interface for your data using HTML and a web language like ASP. I've got a couple of seminars (here, and here) on how to do this. It will require the most conversion and setup, but it provides - in my opinion - the best end result.