Just because I can't think of anywhere else to pose this question:
When writing ASP what is the diffrence when it comes to connecting to a MySql DB as opposed to conecting to a Access DB? Is the connection line the only thing that's different or am I going to have to dramaticallt alter all my code?
I don't know why but i've always found a mysql db more stable when it comes to lots of users being online and/or having a lot of records (this is probably just my hosts fault as both TDC and KM seem to run fine...)
I'd recommend MySql over Access. Access is only good for very small databases, such as in a small site like mine. Any bigger than that and it easily crashes or can't handle the load.
Access was designed before PHP/ASP for use in offices to store data. Then someone went and hacked a server side plugin for it, so it's a bit shakey round the edges.
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
AFAIK there's no difference in the actual scripting. You have to connect to the database a different way, but because the scripts usually use wrapper classes, you can use the same code for multiple database types.
Circy: If I wanted some 7 page nerd explaination I would have asked at one of the ASP tutorial sites that came up when I was looking for info. However because I don't care how ASP and MySql work server-side and ODBC, ADO, ISS, ODB... whatever other random strand of letters that may be thrown at me in a programers forum don't really help me much. So I asked here assuming someone like Jannis, Club, or Kris would give me a quick to the point explaination.
"So I asked here assuming someone like Jannis, Club, or Kris would give me a quick to the point explaination."
Whoa, my name's in there
Your questions got answered but I'll add my two cents nonetheless In fact, I did with KM2 what you are going to do now (switching from Access to MySQL although lots of lines were already written). I didn't experience any problems. Getting a MySQL DB up and running on both, your own pc and your server can be trickier than you might expect, but you won't have to change much within your code. Just like Tigs said and just like you assumed in your first post, all you have to do is change your connection - that's one line you have to alter. I did not have to change anything else, all other code parts just kept working like they were supposed to.