Fix reading Memos written by Lotus Approach #74
Conversation
This file contains hidden or 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
Lotus Approach uses dBase IV files, but the DBT files it produces use a different header and a different storage method. In this case there's no separation character but the length of the data is exactly the length given in the header minus the length of the header itself. To avoid 8 extra, usually zero, bytes at the end of each memo when reading this database we now check the reserved field in the header and use the alternate handling for this version and the original one for all other versions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Lotus Approach uses dBase IV files, but the DBT files it produces use a different header and a different storage method. In this case there's no separation character but the length of the data is exactly the length given in the header minus the length of the header itself.
To avoid 8 extra, usually zero, bytes at the end of each memo when reading this database we now check the reserved field in the header and use the alternate handling for this version and the original one for all other versions.