Skip to content

Releases: joyfullservice/msaccess-vcs-addin

v3.4.22 Bug Fix

02 May 20:07
Compare
Choose a tag to compare

Bug Fixes

  • Resolve a source file encoding conversion issue affecting the export of Table Data Macros. #324, #325

v3.4.21 Bug Fixes

29 Apr 14:37
Compare
Choose a tag to compare

While most of the development efforts are going into the upcoming version 4, I am rolling out an update for the 3.4 release to address some specific issues reported over the last few months.

Bug Fixes

  • Resolve an issue when canceling a running operation in certain scenarios. #291, #293 Thanks, @hecon5 and @jhgarrison!
  • Support printer names that are longer than 32 characters when building from source. #313 Thanks, @Tanarri!
  • Properly encode ampersand character in XML output file. (Technically an Access bug, but we are able to work around it.) #314 Thanks, @alanv73!
  • Fix issue with the exporting of table data macros. (Regression bug) #324 Thanks, @alanv73!

v3.4.20 Export MSForms 2.0 form design as JSON

26 Jan 22:17
Compare
Choose a tag to compare

Enhancements

  • While rarely used in Microsoft Access, traditional VBA forms (Microsoft Forms 2.0) can be used in Microsoft Access databases. This update adds an additional exported source file (for reference) which shows the form design in human readable JSON format. See #297 for details.

Bug Fixes

  • Switching from a local table to a linked table with the same name can create an orphaned file in tbldefs. This caused build errors when the add-in attempted to import both the local and linked versions of the table. Thanks @jhgarrison for pointing this out! #296

v3.4.19: Export path bug fix

29 Nov 15:12
Compare
Choose a tag to compare

This update adds an additional bug fix to the previous release.

Bug Fixes

  • Fix support for custom export paths. #284 (Also related to #273, #281)

v3.4.18: Fix build path

09 Nov 14:27
Compare
Choose a tag to compare

This update incorporates several minor bug fixes from the dev branch.

Bug Fixes

  • Fix support for absolute export paths. (While a blank or relative path is recommended, some users prefer to use an absolute path for exporting source code.) #273, #281
  • Standardize hash generation to use UTF-8 byte arrays to match other SHA-256 hashing tools. #278

v3.4.17: Minor bug fix

23 Sep 16:36
Compare
Choose a tag to compare

Bug Fixes

  • Enhanced the JSON encoding function to properly escape special characters used in key names. Thanks, @jhgarrison for reporting this! #259

v3.4.16: Minor bug fix

10 Sep 14:12
Compare
Choose a tag to compare

Bug Fixes

  • Resolved an issue with two options combo boxes that were not loading correctly in some non-English environments. Thanks, @Geforced for reporting this! #258

v3.4.15: Major update

21 Jul 15:36
Compare
Choose a tag to compare

Summary

This has been a long time in coming, but today we are releasing the 3.4.x version of the add-in! Containing over 100 code commits, this version includes numerous bug fixes and enhancements. Some of the most notable changes include the transition to VBE format for code module exports, the ability to build a database containing non-compiling code, reduced change "noise" between builds, improved International language support, formatted XML, multiple embedded theme support, and export of extended table properties.

I won't attempt to describe each change in detail, but below are some of the highlights:

Enhancements

  • Class modules are now exported using the .cls file extension. This is more consistent with the native VBE export, and provides an easy way to differentiate between standard and class modules in the source files. Legacy class modules are still imported correctly since the module type is determined from the content rather than the extension.
  • Module files are now exported and imported using VBE instead of SaveAsText/LoadFromText. This allows us to export a more universal file format that you can drag and drop into a VBA project, or drag and drop from a VBA project to the file system. Additionally, this now support hidden VBE properties (such as default members or descriptions) not visible in the VBA source code.
  • Non-compiling code can now be used when building a database from source. This is important when doing collaborative work where the newly built database may require additional code changes to be able to compile. (In the past this would throw an error or fail to complete the build.)
  • Dynamic theme colors are now sanitized in the source files with multiple levels available in options. This resolves a long-standing issue where builds on different computers would produce slightly different exports. Special thanks to @hecon5 and @A9G-Data-Droid for their help in building and testing this important enhancement!
  • A complete list of codepage mapping is now included in the add-in, so if you use an International codepage to allow non-english comments in source code, the comments are now correctly translated to UTF-8 for version control, and back to the local code page for import. Thanks, @tst32 for helping make this happen!
  • XML data is now formatted with indentations, making it much easier to read and compare.
  • With the improved XML sanitization function, table definition exports now include extended properties (such as description text), allowing these properties to be used when rebuilding from source.
  • MSysResources table is now created using native Access functions instead of the less predictable temporary form object.
  • Added the ability to cancel an import or export operation and still write the log file.

Bug Fixes

  • Fixed an issue with custom themes not being added, particularly if multiple themes were involved. #240
  • Newline characters are now properly substituted when exporting table data as TDF. #251
  • Eliminated save-as prompt when importing non-compiling module objects. #236
  • Fixed build errors with VBE Project properties used by RubberDuck. #226
  • Resolved export path issue. Thanks @Tanarri! #214

Other Changes

  • PLEASE NOTE: Due to some changes in export file formats, you may see a large number of changed files the first time you run an Export after upgrading VCS. Note that VBA classes will use the .cls file extension going forward. (Git should automatically handle those as renames)

v3.3.17: Improved multi-lingual support

19 Mar 16:07
Compare
Choose a tag to compare

Summary

Most notable in this release are the removal of the legacy "encryption" feature, the option to select a hashing algorithm, and numerous updates relating to Unicode support.

Special thanks to @hecon5 and @A9G-Data-Droid for some significant contributions to this release!

Enhancements

  • Discard unneeded column metadata when exporting pass-through queries. c098927
  • Remove user information from connection strings when using Trusted_Connection=Yes #181
  • Support other types of path separators besides \. Not technically needed yet, but would be helpful if the add-in is used on another language of Windows, such as Korean. f3a70e1
  • Refactored the Unicode conversion to use the ADODB.Stream conversion rather than API calls. This simplified several complex areas of code and helped with a slight performance increase. We also changed the output to always use the UTF-8 BOM in export files. Thanks, @A9G-Data-Droid for your work on this! #186
  • Referencing the active code page in Windows rather than relying on _autodetect_all for converting VBA code modules. (The autodetect may guess wrong when large numbers of certain extended characters are used in comments.) d84d8b7
  • Added option to select hashing algorithm, now defaulting to SHA256 instead of SHA1. ecbb392
  • Enhanced debugging capability in add-in using a new option to break on errors. 1713533
  • Added option for greater precision in performance logging. Thanks @Tanarri! 1150841

Bug Fixes

  • Fix index date comparison. 284b154
  • Use explicit reference to FileSystemObject. Thanks, @Tanarri! #180, d9f62e3
  • Fixed paging issue in concatenation class. Thanks, @Tanarri! #194
  • Removed (little used) RC4 encryption feature for potential security reasons. Thanks @hecon5! #193

Other Changes

  • PLEASE NOTE: All export files created by the add-in now include a UTF-8 BOM, so you may see a large number of changed files the first time you run an export from the updated add-in.
  • Legacy RC4 Encryption Removed If you were using the Encrypt option with any of your projects, you will want to review #193 and this page for some important changes in this regard.

v3.3.1: Important Bug fix

23 Feb 20:28
Compare
Choose a tag to compare

Bug Fixes

  • Unmodified source files would sometimes be deleted when running an export with Fast Save on. #179
  • Improvement to log file output terminology. 0961caa