Replies: 1 comment
-
Rubberduck isn't exporting the modules, it just tells the VBE to do it, and then the VBE does whatever it normally does when you export a code file. The VB_Name attribute should not contain a file name, but a legal identifier for the module (the file is named after the module, not the other way around). If the value somehow isn't a valid name for a VBA module, it could be why it causes issues. It's where the programmatic name token comes from, and every module has it. So no, Rubberduck isn't doing anything special to export that line, and if we did anything to "fix" it then the vanilla export functionality in the VBE wouldn't be working exactly the same, and to me that would be even more of a problem. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a way to disable writing the first line "Attribute VB_Name ... " into each file exported
This line breaks my code when i reimport the file and it contains only the filename.
Maybe i am missing something ?
Beta Was this translation helpful? Give feedback.
All reactions