-
Patch Lady – keeping track of Access issues
A recent question of the forum reminded me that there was a recent post I saw about issues migrating to 1803 and it’s impact to Access databases. As I posted in the forum post the situation was as follows….
“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 his data 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:0000Sources for these reg edits below:
1803 UPDATE SERIOUS ISSUE
Microsoft Access Database Corruption
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’
Not this is not the same as the Access 97 bug that impacts all Windows platforms with data tables longer than 32 characters.