Killing Access

Well, today marks 2 months since I started my experiment of killing MSACCESS.EXE every couple days instead of having to reboot Windows once a week. I'm pretty confident at this point that the problem is a memory leak inside Access itself.

Two months. Zero problems. Issue solved.

LLAP
RR

P.S. And I'm not saying that Access is completely to blame. It could be something in my own code. This is a database that I've been building and upgrading and modifying since 2002 and there's lots of spaghetti code in it. I'm sure there are object variables that I set and didn't forget. So I'm not saying that it's Access' fault. The problem could be mine, but at least I've come up with a good solution.

Hunting down every questionable bit of code in this database would take weeks, if not months. Plus as I always say, my database is a bit like Scotty's engine room. It normally hums along just fine but in some places I've got wires running around like Christmas tree lights. I'm like the mechanic that drives an old beat-up car because he's constantly tinkering with it. Sure I teach you guys how to build good databases but me from 24 years ago is nowhere near as knowledgeable as me from today.

And I ain't got the time to clean up his mess LOL.