[DBC] Fix for DBF long field names that collide after 10-char truncation.#1964
Merged
Conversation
…into FabDBC_Work
…ENAME TABLE in DBCs
…into FabDBC_Work
Fix some related functions
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If two long field names share the same first 10 characters (e.g.
CustomerAddressandCustomerAccount→ both becomeCustomerAd), the physical.DBFwill have duplicate field names, which is invalid.VFP will shorten the FielName and add a numerical index at the end, We are doing the same thing