I have pretty much completed an microsofr access project which is a stock control system. It includes tables, forms , reports, queries etc. It also have a front end on for easy navigation for my uncle (it's for him). It will allow him to add, remove, edit entries in the table and run reports of the current stock situation.

I want to put this on the Internet, so he is able to do all the above wherever he is basically.

Just slightly confused about putting it on the internet now. What would be the best way to do this, obviously using ASP is the solution, but what application shall I use. Could it be done in frontpage with aspx files which would trigger the .mdb to be opened through the webpage? Or isn't it as easy as that.

Thanks in advance

Depends on how many people need to access the page simultaneously. If it's any more than about 2-3, anything built in FP will choke and slow down your server.

The best way to code ASP is to learn how to hand-code it. You can build your basic page structure in FP if you don't know HTML well (but if you can build an Access project, you can learn HTML), but ultimately you'll want to hand-code the app. Notepad++ (I forget the link) is a really good free colour-coded editor that way.

Here are some other resources (besides chrishirst and I) to get you started:

www.asp101.com
www.haneng.com
www.4guysfromrolla.com

One thing: you're pretty much restricted to your tables if you put it online using ASP. Reports don't work, forms don't work, and queries don't either. So you'll have to recreate those.

It may be easier for you to put the database onto a machine that you can access remotely and set up Dynamic DNS for it (www.dyndns.org).

I'll second the recommendation to get Notepad++ it's really a great editor. And open source, which means it's free and generally well written. You can download it here. That said, I actually have a chance to disagree with the wise and mighty Adam. Even if it's only on three minor points.

First, I'd advise you to build an ASP system, instead of setting up Dynamic DNS. Simply because you expressed interest in doing that, you seem intelligent enough to be able to, and it's a good way to build new skills. Adam is of course right this is not the easier path to take, though. He's right about avoiding FrontPage, but I don't think you need to do it completely by hand. In fact, I'd suggest using Visual Web Developer, available here from Microsoft. It's free, and it's pretty good at designing web stuff, and has intellisense. It works on ASP or ASP.NET, although it's really more geared toward .NET.

Finally, Adam is right in that reports ( and forms ) don't work for what you're trying to do; the whole point is to recreate them in web format. But queries will be available to your code, and they'll act like tables ( except action queries ). If your Access report is based on a query, you can still read data from it in ASP, and then just output the data into html.

Out of curiosity, when you say you made an Access Project, do you mean using Access as a front end for SQL Server?