I mentioned security just because in this fun season of auditors it's all I heard about. But anyway, to clear some things Jim didn't touch on, here's how I would go about doing this.
This is a 3 part question really.
What OS am I running ? You have different options depending on what OS you choose. I mean If it's a Unix varient then you can use Ruby,Java server pages, PHP (recommended), PERL, etc... as your web scripting language (although perl just parses and output's pages, not really a web scripting language). On the flip side, you could be using a windows server, in which case you can be using ASP, ASP.NET (Which is very easy, point and click database connection and data pulling, wizards, etc...) and others again such as php, perl, Java server pages etc...
What Webserver am I using ? If you are in the windows market chances are you'll be using IIS since it comes preloaded in most systems (Server and desktop). You could also go with with others like apache, which can run different modules like JBOSS for Jsp pages, etc... On Unix, i'd stick with apache, anything else could be trivial for a new user not used to the idea of config files and services that don't have fun GUI tools (allthough appache has a billion).
What Database am I going to interface with? This is another big question, as you need to think out how your tables are layed out. If you make a design that doens't follow the normal rules (or atleast 1,2,3 and Boyce Codd if your feeling adventures) then your asking for redundancy problems later (2 records that you have no idea which is the real, relavant date) as well as expansion problems (doing 10 thousand updates on a table instead of switching the foreign key record to reflect the new changes) If you have no idea what i'm talking about, it's not hard but a something you have to relize. Anyways, on that note, you have options as well in DB's, postgrl, mysql, if you have academic licenses MS SQL Server (recommended for ease of use), access if you hate your life hahah, etc.... I like Mysql the best, but it has it's issues, and they are documented.
Now How would I As a newbie go about this ? Despite this forums general tag-lines, I would use ASP.NET as you could purchase a 30 dollar asp.net in 24 hours crash courses for idiots and the blind and come up with something fast. As well though You could pick up a very good php/mysql starter book, I had one years ago can't remember the name off the top of my head. Just glance through to make sure they go over table creation, idea's to stick with, I mean it won't be any college level DB class, but just the basics for a basic program.
Cheers for beers
Eodlabs