Urgent! Site running on Access MDB's down

I have a storefront running on the latest IIS with an Access MDB using an ODBC DSN. It also hits some assorted other dsn-less MDB connections.

It has been running fine for a year. All of sudden last week, all pages related to any access DB, simply time out. They just load forever. ANY access data source, even a test one I uploaded to make sure I wasn't going crazy, just didn't respond.

I tried all types of corrective actions, such as disconnecting the DSN's, backup MDB'S repairing the MDB's etc. to no avail. Then it fixed itself.

Now, again today, the site is out, database-wise. No explanation. Does anyone have an answer to this problem other than 'use SQL' (we're working on it).

The only external factor thats changed is a heavy spike in traffic. I have not mucked with any settings lately. My ISP is not available on weekends and I am losing money, please help..!

Perhaps something was changed or updated on the web server. Any errors in the event logs?

I had problems with access... I found the database was bloating in size rapidly everytime a query was run, is that happening to you (and might that be the cause)?

Yeah it's a turkey. I have to reset my stats package every few days to deal with DB bloat (read: slowdowns)

It's really strange what's going on with my server. I tried putting a static index.html test page, and even that just does an infinite load.

I have thousands of static sub-pages on the site and they are all working fine. So can I assume that someone is doing a DoS on the index page?

I really wish my ISP guy wasn't away for the weekend this is driving me nuts, an article about my site just came out in a big magazine this week and it is NOT the time for a broken site!

I've just been using a third party stats generator (which are also inaccessible currently). I haven't a clue how to meaningful process the raw logs.

I meant the windows server event logs, not the web logs.

Oh, no I don't have access to those. It is a hosted package at an ISP, and unfortunatly the trade off with them is that because it's a small ISP, their service is great on weekdays, but they don't have 24/7 support.

Meanwhile I've got hundreds of dollars out the door..

If you didn't change any code it sure sounds like a server-side issue.

Maybe a host with 24/7 support would have been a better choice