I tend to export to BASIC (.bas) files, which are text format.
If you reference the runtime for Visual Basic Applications Extensibility (I'm posting from my phone - so it may not be named exactly that - but should be close) you can write code to iterate over all projects and code panes etc and export the code to .bas and .cls files as applicable. I do this for excel especially -- every time I press {ctr}{b} it creates a dated folder hierarchy with exported code. O.o
Your forms re DCL are saved in the file as well, not to mention the forms are interactive rather than write code and test.
Nice thing is you can group your code under a heading for a common theme and jump to just that group of code. Where as in lisp you would have to say scroll down to the top defun level to see all the functions in that group.
Lee can you do this in VLIDE?
...but more important is to be sure what routine is doing from beginning to the end and to spot where such problematic portion of code was written to correctly...
But now I'm trying to getting started with VBA and this issue is the first drawback for me:All vba has to be compiled to run. I don't see what you are worried about. If you have an older dvb, opening it in a newer version of vba will automatically upgrade it. I've never had a problem with leaving my code in a dvb for the last 20 years.
Obviously you create few modules/userforms and write some codes inside, then save the whole project as .dvb file (ctrl+s).
After that you close AutoCAD and start a new session again, deciding to reopen the project you previously wrote, but the only way I found is to try importing the .dvb file so I'm ending up with a compiled s*it...
So whats the proper way to maintain VBA projects (codes) ?