Of those of you that have experience creating macro features how do you feel they compare to using equations? Do you think there is a performance gain or loss? We have some templates that use quite a few equations and I am considering converting them to macro features but I am afraid that there might be a performance hit. I like the idea of the macro because I can have one central place to go and update our calculations rather than having multiple templates that will need to be edited and using a macro gives greater flexability to the programmer, you can do more with the output from the macro than the output from an equation.
If I have multiple sw documents with this same macro feature embeded and these docs were in an a sub-assembly and that sub-assembly is in turn in a higher level assembly what would happen if I opened the higher level assembly and hit rebuild? Would the macro feature for every document contained within this top level assembly and every sub- assembly execute? Do the docs have to be fully resolved in order for the macro to execute? If everyone of these macro features executes on every rebuild I would be concerned about the performance of the assemblies.
Would a document that has 10 equations perform slower or faster than a document that has those same equations in a macro feature? For comparison I am thinking about time to open, fully resolve, rebuild, save then close.
Thanks to anyone who has a comment.
Sam