A family of Microsoft relational database management systems designed for ease of use.
- Do these changes require administrator rights?
- Can these changes be made thru VBA?
- Can these changes be made just for the current msaccess session?
Thanks!!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted. We ran compact and repair. But it still getting corrupted again and again. This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.
Is there anything i have check in new windows update or any other step to prevent database corruption?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thanks!!
I agree this client side change works and may very well have saved my business. The next important question is has anyone experienced any negative side effects to the database in question or any other applications or Windows itself after making this change? I do like this approach because I do not have control of the server configuration.
So the best advice to everyone. Make this change now to ALL Windows clients involved (and reboot) and your problems should cease. That is a until a new Windows 10 client without the change is introduced or the registry change gets overridden.
The server side change to one share I suggested has appeal if you have control of the server. Change just one place and it does not matter what the client side looks like.
Having said all that, Microsoft has to fix this. We should not have to go through this pain or have to apply these band aids. And who knows how long they will last. We have some fixes, but we need leadership from Microsoft to do ROOT CAUSE ANALYSIS and permanent CORRECTIVE ACTION. Basic problem solving technique.
Is Microsoft even listening anymore?
Microsoft has proven by its inaction that they don't give a flying flap about this issue. After 2 years that the issue has existed they expect us to believe that they can't even reproduce the problem....let alone fix it. That beggars belief and I just don't buy it.
That's fine as an opinion, but did you apply the DisableLeasing remedy and are still having problems?
That's fine as an opinion, but did you apply the DisableLeasing remedy and are still having problems?
Yes I have and it works fine. My issue is that it's a workaround at best, and who knows when it will break? MS is very good at breaking things as evidenced by the recent update query debacle. Testing seems to be a thing of the past. The users are the test bed.
It is beyond the bounds of credibility that they can't replicate this issue and then provide a proper fix after *2 years.*I'm not sure who they think they are kidding.