Access Database is getting corrupt again and again

Daniel  -  Every week I deal with a couple of these and have to defend my credibility.  As it stands I'm awaiting approval on a contract to assist in migration of my software currently in use at a large number of police academies and agencies that track LE training down to a micro level; something of more significance today than ever.  I don't think Microsoft understands the scope and sophistication of the applications that we developers are creating in Access and their importance.  Perhaps they think we are all just doing Northwind?

Sadly, there is no solution (yet) .  We have a couple workarounds, but 2 years in still no proper fix and not sure if we'll ever get one. You would have thought, erroneously, that such a catastrophic bug would have been priority no. 1 for Microsoft and addressed promptly, yet here we are 2 YEARS and waiting. I'm sorry to say that I've actually started migrating some of my clients away from Access at this point.  Things have become too unstable with Office and Access that they can no longer be counted on.  It's bug after bug, and no fixes leaving the developer holding the proverbial bag and looking incompetent in the eye of their clients.  And then Microsoft wonders why IT departments hate Microsoft Access, seriously !? 

I used to track bugs on my blog and have given up because there are so many, that alone would be a fulltime job to do properly. 

Sorry about the rant, but just tired of the same old, same old from Microsoft. 

Something seriously needs to change internally at Microsoft. 

I need coffee.  :-)

I have Repair and Compact option on Close checked in my backend db, which helps with the bloating. I agree with Daniel on importing your db to a new blank db from time to time, to keep the size in check.

Btw, my switching to another backend folder has been working out ok for the past couple weeks. Only one corruption incident so far.