Access Problem

Since Dec 13th I have had an ongoing issue with my website having to recycle my app pool several times a day manually.

Because I had just added 3000 records to the Access db (a 15% increase) and had made changes to my website that put additional strain on the db back in Nov, and was having some other problems with db because of another issue, I naturally assumed the problem lay in my court.

However as I have tried to troubleshoot this problem, the more it didn't seem make sense in the bigger picture given the severity of the error (although the coding is far from perfect, it worked and the website has pretty much performed error free for the last seven years or so).

Then the other day I came across this dated 15.12 http://community.discountasp.net/showthread.php?t=11946 Coincidence? I dunno. But to be honest I am at my wits end and was pretty close to tears the other day out of sheer frustration.

The ldb table can't seem to get far beyond 1k> before the whole site comes down. So much for the 16K lock and 255 concurrent users.

If anybody can help me with this issue it would be much appreciated.

 

...Truth is while Access does work you do have to juggle it at times.
Crazy I know but it is not intended for robust usage on-line.
So if you don't want to move, or can't, to SQL Server, we need to go over some options.

It appears you are ready to accept the concurrency problems.
So what can be done? Well, without seeing how your code is working I'd first suggest chopping.

Chopping? Yes. Split your Access DB if you can.
If you can't...Well, I'm not sure what to suggest to be honest.

Want me to look at the code?

 

Sorry Wisemx

What do you mean by "Chopping? Yes. Split your Access DB if you can"?

 

Yes. I know it can't always be done but I've had to do that for many folks.

 

"Split your Access DB"

Could you just provide a little more detail, how would you propose to split a db?

 

...This would require a small book, many methods can be used.
Most common, let's say you have two tables in that DB.
So you create another DB and in the new DB you create one of those tables.
Then you code it so you are using something for one and something for the other.
OK, sounds like I'm related to Dr. Seuss. ;-)

But you get the idea, right?
All the best,
Mark

 

tant, as Mark has said, Access was never really meant to be used in a web-based application. I think things would go a lot better for you if you bit the bullet and moved to SQL. Those 25,000 or so records that are choking your Access database would be nothing for SQL to deal with.

I know it can be painful to make a switch like that, but it would certainly be worth the effort in a case like this.