Did you get anywhere on this query or using VBA Scripts with Solidworks?
Its been a few months since I wrote a VBA script within an EPDM SWTaskAddIn. If memory serves me, here are my basic observations...
-You have to write one big long script file. Anything valid in a standard VBA file is allowed within this script.
-You cannot reference or add additional classes, structures (files), but you can define multiple functions/subroutines within the same script. I suspect you could just as easily define multiple enumerations, classes, structures etc., as long as its within the same script.
-You can't statically reference external DLLs and such, but you can dynamically load them within a script. So, you can dynamically load external components. Or, create your own VB.NET project, place the bulk of your code in there (with classes and all), and then dynamically load it within the script to run.
-There's no facility for debugging a script within EPDM, as it simply hands it off to a SolidWorks station and executes. However, you can develop the script locally on your computer within the SolidWork'ss VBA environment; test, develop and debug, and then paste the final source code into the script window for the task within EPDM. This is what I did.
Definitely some draw backs, but you can accomplish pretty much anything you put your mind too.
Hope this helps... hope its accurate.
Greg, check out these KB resources:
The thing to keep in mind is this: EPDM Task script is running as an EPDM script but the advanced scripting engine is actually a SW VBA7 macro so be sure to distinguish between the two in your VBA7 calls.
I wrote one to make EPDM calls as well as SW macro calls on the document being converted.
I used data card field values in the EPDM task script and it did well.