MS Access Files corrupted by Win10 Update

Topic

New Reply

Apparently a recent Windows 10 update around November corrupts networked access databases.  Does anyone have any information?  It’s driving us nuts!

Edit to remove HTML. Please use the “Text” tab in the entry box when you copy/paste.

Reply | Quote

Replies

To be able to help you, we will need what versions of WIn10 and MS Office you are using. We also need some information about the structure of your network.

Reply | Quote

There’s the issue whereby older Access 97 can’t be opened with all versions of Windows …or.. hang on let me go and get a past link I saw…

This is the info for the bug introduced impacting Access 97:

Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.
Use one of the following options:
Option 1: Modify the database to ensure that all column names are less than or equal to 32 characters.
Option 2: Convert the database to the .accdb file format. To use the .accdb file format, you must change the Connection string after conversion.
The easiest way to convert is to use Microsoft Access 2010 or earlier.
Use Microsoft Access to open a database that has an older file format.
You will be asked if you would like to convert. Click Yes and save the database with the .accdb extension.
Option 3: Convert the database to a newer .mdb file format. This doesn’t require a change to the Connection string.
Use Microsoft Access to open a database that has an older file format.
You will be asked if you would like to convert. Click Yes and save the database with the .accdb file extension.
Open the .accdb.
From the File menu, click Save as and select Access 2002-2003 Database.
Microsoft is working on a resolution and estimates a solution will be available early February.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Elly

Reply | Quote

“Client has a database app written In MS Access. It imports data from an Excel spreadsheet using a macro. Reportedly, when the client O/S is 1803 the import corrupts he data ears and it needs to be repaired. Not so when the client O/S is 1709.”

To fix this the person did:

Add the following Registry Values:

Windows Registry Editor Version 5.00

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

“FileInfoCacheLifetime”=dword:00000000

“FileNotFoundCacheLifetime”=dword:00000000
“DirectoryCacheLifetime”=dword:0000

Sources for these reg edits below:

1803 UPDATE SERIOUS ISSUE

https://social.technet.microsoft.com/Forums/en-US/3cd934cc-cbc3-4bdc-8c29-8e486528ce9f/1803-update-serious-issue?forum=officesetupdeploylegacy

 

Microsoft Access Database Corruption

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_win10-mso_2016/microsoft-access-database-corruption/e933f760-f7f2-4b3e-9bc3-0061d5073219

Access – Bug – Database is in an Unrecognized Format

https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/

Access reports that databases are in an ‘inconsistent state’

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%ef%bb%bf-7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US

 

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

PKCano

Reply | Quote