Skip to content

Add ImportExportEncoding to Access add-in settings form - #96

Merged
josef-poetzl merged 1 commit into
devfrom
feature/access-add-in-import-export-encoding
Nov 17, 2026
Merged

josef-poetzl merged 1 commit into
devfrom
feature/access-add-in-import-export-encoding

Conversation

@josef-poetzl

Copy link
Copy Markdown
Member

Summary

  • New combo box ImportExportEncoding in the settings form AccUnitUserSettings of the Access add-in, below ImportExportFolder: UTF-8 with BOM (0, default) or ANSI (1).
  • The form loads and saves the value through IUserSettings.ImportExportEncoding (added in Export test classes as UTF-8 with BOM and detect encoding on import #94); numeric values are used, so the code does not depend on the enum member names in the type library.
  • The .form file is the msaccess-vcs export of the rebuilt add-in, so a merge build works.

Tests

  • Add-in built from source, new core DLLs/TLB in the local lib folder.
  • Form opened in Access: value loaded from the setting (0), set to ANSI and saved -> user.config Ansi, reopened -> 1, set back to UTF-8 and saved -> Utf8Bom, reopened -> 0.

Combo box with UTF-8 with BOM (0) and ANSI (1) below ImportExportFolder; the form loads and saves the value through IUserSettings.ImportExportEncoding.
@josef-poetzl
josef-poetzl merged commit 28f3811 into dev Nov 17, 2026
1 check passed
@josef-poetzl
josef-poetzl deleted the feature/access-add-in-import-export-encoding branch November 17, 2026 17:40
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