Access Database is getting corrupt again and again

Did you implement the disable leasing registry workaround?

Had been working fine for many years. I have been getting an 'unrecognized database format' starting about 1 1/2 months ago. I was getting regular updates for my windows 10 computers.  The crashing occurred many times on a network with 11 users (not all using access at the same time).  At first it happened a few times a day. My network guy changed the computer that seemed to cause the access program to crash back to windows 8. That person stopped causing the crashing. Then someone else crashed it. My network guy changed 2 computers back to windows 8 and now someone else on the network is causing the issue. All seems to be happening at the end of the day when someone is adding a new record.

Sorry the above post is long & rambling, I have been unable to post & simply copied & pasted my notes because every time I tried to reply, I got Opps, something went wrong try again & was expecting the same. Oddly I could not post under Bignose2 as I have before no problem, this is another MS account & it worked so not sure why this community won't accept. no sign of issues or locked or anything. Sorry, rambling again.

Anyway I have done quite a few tests & in the past by now sure to have had corruption so very hopeful, 1809 prob will break something else!

Hi,

1809 seems to have fixed this problem but currently more testing but previous to this I had written below..

I have so far had success with ITYIPMan's suggestion as below & not yet tried DisableLeasing.

Much to my annoyance both PC's auto updated to 1803 (from 1709) despite my Win 10 Pro PC as deferred? and my Home PC on Metered so I thought I would try again (especially as too late to roll one back!)

My server (very average) PC however is Windows 8 but both networked FE's are Windows 10.

Did the reg fix as below & no corruption yet. I have a test loop that I run & it does X number of rapid form updates that I know are written to the BE. 

Before the reg fix it would crash, usually after just a few loops, however sometimes 50 or so,

which is very frustrating for testing. have done 300 loops about 5 times, whilst the Server PC FE is doing the same (not on the same record though).

Tested on my second PC now & also been using as normal & 99% sure OK & would have corrupted by now.

Does not seem to be any performance hit at all but my use if fairly slow & easy & only 3 PC's a the same time & that is very minimal.

ITYIPMan

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

"FileInfoCacheLifetime"=dword:00000000

"FileNotFoundCacheLifetime"=dword:00000000

"DirectoryCacheLifetime"=dword:00000000

What is annoying is I have another PC for backup & testing, I rolled back to 1709 ages ago. Would like to put 1803 on to test but it does not offer the update now, if I use the upgrade assistant it wants to go to 1809 & I really don't want to open that can of worms yet although it would be interesting to know if perhaps this has fixed any of the Networking & corruption issues.

To be honest not searched for anyones experience of 1809 & these access corruption problems, I guess as they had quickly pulled this update no one really wanted to risk this with threats of lost files!!

As being rolled out again I wonder if worth a go. In fact might try on my test PC shortly.

Update: 1809 (October update) seems TO WORK OK but more testing to do

I had server PC on 1709 & client on 1809 & no corruption.

Then updated server to 1809 also, so both PC on October Windows 10 update

So far NO corruption.

These are not my usual PC's but have used for testing in the past when I was investigation 1803 I could easily replicate the setup & 

get the corruption within minutes. They have been rolled back & re-updated.

Made sure there is no residue of the regfix hidden away & was never installed on the clinet PC anyway.

Will try on my main, normal system shortly but if I was a betting man I would say 95% sure this is now OK, but very surprised.

FYI, ACCDB files don't make any difference.  I only distribute .accdb files and this issue affects my users.