A family of Microsoft relational database management systems designed for ease of use.
When the company tells you they're wanting you to log into their VPN & keep their Access database applications running,
it's best to comply.
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.
When the company tells you they're wanting you to log into their VPN & keep their Access database applications running,
it's best to comply.
I will consider your suggestions, but I am keeping an open mind about SharePoint, just like I did about downgrading to Access 2013.
George
Hi George,
I think that the number of Access applications which could successfully be converted to Sharepoint is extremely limited. In my experience, SQL Express would be a much better bet in nearly all scenarios. Give both a try and let us know how it goes!
Regards, David
Hi Mark, David and Shane
For the past few months, I downgraded my users to Access 2013 for my Access database app. The amount of data corruption issues did go down, but there are still issues with performance and data loss, especially with our current VPN.
A database designer/analyst in another department suggested migrating the Access backend database to SharePoint, which he has done successfully with several of his Access databases. He says the performance & data losses has improved dramatically and has not encountered a data corruption issue on the backend databases since moving to SharePoint. Note he did mention that tables need to be converted to "list tables" when migrated to SharePoint and that the 2 GIG db limitation still applies in SharePoint.
We will be having a follow up, "deep dive" meeting with this database specialist, to get all our questions answered and be assured this is a viable option which complies with company policies.
George
If you find an easy way to migrate relational tables to SharePoint can you let us know? I've had very limited success.
Running Access over a VPN is never a good idea and is known to be a potential cause of corruption.
SharePoint is one option, but personally wouldn't go that route because of the list limitations. If you are going to migrate,. Which makes a lot of sense after this issue existing for more than 30+ months now, I'd be more looking at SQL Server (Express) or SQL Azure, or another RDMS. True Enterprise grade database, which SharePoint is not. Keep a database, a database!
SQL Server (Express) -> Local Instances
SQL Azure -> Web, if you're looking to share with users all over the place