Modules not created with their correct names when using "Build From Source" #377
-
Hi! And I found this in Build.log: Is it related? Best Oliver |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
I think it might be due to .bas files on my system are encoded as UTF-8 and not ANSI and Access seems to need ANSI encoded files during import. Because the same issue happens when I manually import the .bas files to a project. |
Beta Was this translation helpful? Give feedback.
-
@ollypsilon - The To answer your question on the modules, after much discussion and review, the most robust source code export seemed to be that of using a UTF-8 BOM so that software applications would universally recognize the encoding of the VBA source content. I think maybe what might be the easiest solution here is for me to publish a "pre-release" version from the I just published a binary release of the |
Beta Was this translation helpful? Give feedback.
@ollypsilon - The
dev
version includes a number of enhancements and improvements over the current master branch, so I decided not to try to take the time to build all the forward-compatibility into themaster
branch. Thedev
branch builds easily from any recentdev
version of the add-in, but obviously you need a compiled version to start with. 😄To answer your question on the modules, after much discussion and review, the most robust source code export seemed to be that of using a UTF-8 BOM so that software applications would universally recognize the encoding of the VBA source content.
I think maybe what might be the easiest solution here is for me to publish a "pre-release" version from…