I want to create a folder with commonly used functions so I don't have to copy them into each module.
Using RunMacro2 (2012 SOLIDWORKS API Help - RunMacro2 Method (ISldWorks) ) I can run a sub in another .swp file, but I don't see how to specify an input variable for a function and get the return value.
Am I thinking about this right? Or is there another convention in solidworks vba to do this, such as importing a .swp file into another .swp file?
IMO, it'd be much simpler to copy the function over than try to call function from other macro unless you create a .NET program
You cannot pass arguments nor receive a return from a procedure using RunMacro2. I'm pretty sure the only way to reference external code/functions using a VBA macro is if those functions are inside a referenceable DLL or TLB etc. That's beyond what I've gotten into. I just paste it in like Christian said. I see the benefit in putting all your handy-dandy functions in one spot so you can improve them further and every macro that uses it gets better. I think you're into Add-In territory for that though.
A very crude workaround would be to write the variables you want to pass to a (text) file then when you call the other macro, it reads that (text) file. I put text in parentheses because there are other file types you can write to; I prefer text because it is easier to see what value was passed by opening the file in notepad. Or a little better workaround is to paste the values you want to pass to the clipboard then call the other macro that reads the clipboard values.
Solid Air wrote:
A very crude workaround would be to write the variables you want to pass to a (text) file then when you call the other macro, it reads that (text) file. I put text in parentheses because there are other file types you can write to; I prefer text because it is easier to see what value was passed by opening the file in notepad. Or a little better workaround is to paste the values you want to pass to the clipboard then call the other macro that reads the clipboard values.
Unless you want to pass objects back and forth... :-)
I investigated passing objects 10-12 years ago. Unfortunately I do not remember the outcome. I think it had something to do with excel. Actually maybe you could use excel to connect to SolidWorks and use different workbooks containing different functions that you could pass objects to. You have peaked my interest about passing objects again, I will have to look through my drive of forgotten macros and see what I can find.
I also did think about the passing of objects when I wrote my reply to John. However, he only talks about passing variables; which is what I focused on.
Solid Air wrote:
..., he only talks about passing variables; which is what I focused on.
Variables ⊃ Objects... :-)
Josh,
Variables ⊃ Objects ???
Solid Air wrote:
Josh,
Variables ⊃ Objects ???
The set of Variables is a superset of the set of Objects
I did not realize that was true for VBA. I thought variables (long, double, string, etc.) turned to objects in VB.net. Learned something new today. I supposed that should be expected, the basic class I took was taught using an Apple II+ computer in 1982 .
A variable is anything and everything that immediately follows "Dim" (assuming Option Explicit...)
Hi John,
You create a library of common functions in VB.NET or C# and then add this library as a reference to your VBA editor. here is a VIDEO.
Really cool thing about this approach is that you will have an intellisense in VBA editor.
Regards
Does this library have to be local for each user, or can it be on a network share?
I'm the only one who will be using the code so it doesn't matter where it is
It matters to me. I would like to know the answer.
I believe that the dll will need to be installed and registered on each machine using regasm.exe That happens on the developer machine when the code is compiled but will need to be done on each machine separately.
if you want to create a .net dll that is com compatible, take a look at CADHero .NET Tools for VBA. The source code is on github and is free to use and fork.
GitHub - jliliamen/CADHero-DotNetTools-: DotNetTools brings all the convenience of the .NET framework to VBA into a cent…
DotNetTools for VBA – CADHERO consulting SUARL
Hi John,
You create a library of common functions in VB.NET or C# and then add this library as a reference to your VBA editor. here is a VIDEO.
Really cool thing about this approach is that you will have an intellisense in VBA editor.
Regards