MS Access and HTML

I have a project I'm trying to do which involves putting a MS Access database onto the internet.

I've never used Access before, and Microsoft says that it is easy to put access database onto the web.

Is it actually easy to do, and do I need to learn much about Access in order to do it?

 

ooooo....oooooooooo you can use ASP.

I use it for EVERYTHIng the whole of my website its built with it. You will need to learn how to connect to a database with an ASP page. Kodo also knows a lot about ASP/DB scripting i know. an example of a database on the web: http://www.hypostasis.co.uk/guestbook.asp
loops thru a table in a DB.

 

yep.. moving to programming forum.

The only thing you need to know about access is how to make queries in them. Well, you don't NEED to know it as you can script the queries, but it's faster to use the queries you built in access. FYI, you can create stored procedures in Access 2000 as well.
ASP is your game at this point for access. but you should know it's limitations first.. The biggest one is that it starts to choke at about 20-30 concurrent db connections, so if this is a high traffic site/app, then don't do it. I would suggest SQL server at that point.

 

I know that SQL would be the best way to do it, but the idea is to take an already built application that's used in an office and putting it on the internet for use in places other than the office.

I think that the site may eventually have more traffic than ASP can handle, so that would probably not work to well.

I was just curious what it would look like if I did it, and what it would take to make it work.

 

YIKES!! hold up now.. ASP won't be the problem.. the ASP environment can handle heavy loads just fine.. it's the database drive that can't. i.e. Access' Jet4.0 sp6 Driver can't handle the load. If the database was written in VBA and has a front end to it, then I'm afraid that is useless on the web. You'll have to write a front end for it. So if that's the case, then you're better off using the upsizing wizard to a sql server and building the front end for that...eventually.

 

Ok.

I was kind of hoping I could just export it(like Microsoft says you can) to an XML file and stick it on a Windows server without any additional work. But I guess I may have to get around to learning SQL and put in some big hours. Oh well

 

yeh, what MS doesn't tell you is that you CAN export it , but it's for display only