Access Database is getting corrupt again and again

Yes, with this I can agree, in my opinion the two of us are dealing with two different problems that result in the same way - database corruption, but do not share the same preconditions.

Hi LubomitTrubac

I agree that the problem referenced in the link you provided may be different to the size limit problem I am experiencing - the commonality is the regular typical corruptions. 

I have numerous databases (in .mdb or .accdb format)  on multi-user customers sites that are close to the published 2G limit for Access databases and they never get corrupted. On the same sites, at the same time, a database with a more complex schema always gets corrupted when it reaches 1.2 G, well below the published max size. The only way to fix is reduce the database size by deleting records (not ideal) OR splitting tables across 2 or more database containers (a lot of work and has side effects). Either solution ALWAYS works which makes me think in some situations ACE databases have a lower limit then the 2GBytes ststed by MS. As before I am hoping Microsoft Access team members are taking note of this as it may be a pointer for them to diagnose why these "Unrecognised Database" errors keep occurring. 

Hoping for a comment from the Microsoft Access Team...

I have to disagree, at least from my experience at our company.

Firstly, our database hits most of the time 800Mbytes, never reached size above 1GB. At the time these problems started, I have digged the web for related information and found a forum post that stated: this behaviour is replicable with just a newly created database with single simple table used as BE shared across LAN with single computer running Windows 10 1803. Hence my conclusion that size of the database does not matter really.

Next thing, as I stated before, we have a mixed environment of client computers running both Windows 7 and Windows 10. At the time when regular corruptions started, I have been using a tool to monitor state of our database and everytime it has been a Windows 10 machine that corrupted the database (marked DB as suspect, rendering it useless for the whole company). Also, you can find numerous posts on this topic stating that reverting Windows 10 to previous build solves this problem. Therefore I doubt that any PC running Windows 7 will be corrupting database so often - at least not at our end.  

To be fair, I don't have any Access DB larger than 1GB, so I couldn't verify that database gets corrupted again after hitting the 1.2GB boundary. In fact, we have approx. 20 computers at our site, some with Windows 7 and others running Windows 10 Pro (fully updated) with only the DisableLeasing workaround applied to our server - and everything is running okay for now.

Of course it is not ideal solution, it possibly still has some impact on speed and (as I read somewhere on MS website) amount of network traffic. Another user at some random forum stated that after applying updates to Win2016 on the server, the DisableLeasing setting got reverted - so that is another point of possible failure for us, that we have to watch for.

Thanks for info. The problem on the Win10 version is probably related to the problem I have described but the fact that it is always fixed by reducing the size below 1.2G and this occurs on both Win10 and Win7 hosting the data means applying this would not fix the problem. I was hoping that by posting the details that it might alert/help the Microsoft Engineers working on this problem in finding a solution.

Thank you!  I'll bear this in mind and check to see if the users are reporting any degradation of performance.