Skip to content

VisualFoxPro dbf types need 263 byte added in the header for dbc data… #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

EmanueleBonin
Copy link

@EmanueleBonin EmanueleBonin commented Mar 23, 2025

While creating a visualFoxPro Dbf type, the header is not complete. So the dbf cannot be opened by visualfoxpro ide because VFP dbf files need some extra bytes in the header to describe the dbc database to which the folder eventually belongs

If there is a memo field in defined vfp dbf the fpt file with memo data will be create when dbf will be saved

PR Classification

Enhancement of the dBASE.NET library to improve memo field handling and overall functionality.

PR Summary

This pull request refactors the dBASE.NET library to enhance memo field management and improve code clarity and performance. Key changes include:

  • Dbf.cs: Added DBFPath property, improved Read and Write methods for memo file handling, and updated CreateRecord and WriteRecords methods.
  • DbfHeader.cs: Introduced HasMemoField property and updated header length calculation for Visual FoxPro compatibility.
  • DbfRecord.cs: Enhanced Write method for memo data handling and improved field data indexing.
  • IntegerEncoder.cs: Modified to correctly handle decimal values during integer encoding.
  • MemoEncoder.cs: Implemented a caching mechanism for byte arrays to optimize memo data encoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant