Improved support for Access 2010, 2013, and 2016 #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some Access 2010 files use 0x03 as the version number rather than 0x0103. For this reason I have changed the call to mdb_get_int32 to mdb_get_byte. In addition, according to the Library of Congress page: https://www.loc.gov/preservation/digital/formats/fdd/fdd000463.shtml Access 2016 uses 0x05 as the version number. I have inferred from the Wikipedia page that Access 2013 likely uses 0x04.
|
Bump |
|
Have you tested these with corresponding versions of access files? are the results as you expect? |
|
I have tested with Access 2010 files that do not currently open with mdbtools. The linked Library of Congress page indicates that Access 2016 has the same file format except adding large integer support. I have not tested against these files, but the provided patch is meant simply to identify them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some Access 2010 files use
0x03as the version number rather than0x0103. For this reason I have changed the call tomdb_get_int32tomdb_get_byte.In addition, according to the Library of Congress page:
https://www.loc.gov/preservation/digital/formats/fdd/fdd000463.shtml
Access 2016 uses
0x05as the version number. I have inferred from the Wikipedia page that Access 2013 likely uses0x04.