Frist, I'm a rookie at writing macros. But I have written some simple macros. Here's my question: I want to load my macro on another someone else's computer. But when he runs the macro he gets an error. But it works fine on my computer. The error is: "Compile Error Can't find Project or Libary." Any suggestions? Thanks
Can you attach the macro for testing?, Could be version, or references issues. What is the comparable software and versions on both machines? More info would be needed.
This error is generally due to missing references. Make sure you've correct references in the macro. Update/correct the macro references to your SOLIDWORKS version as suggested here Fix-Update SOLIDWORKS Macro References? (don't worry on the fact that video is for fixing missing library error but check the process to update your macro library). Also uncheck the utilities library reference from the macro.
Perfect!!!! It works now on our computers.
Thanks so much for your help, Deepak. I have read so many of your comments on this forum. And they have been lots of help.
Now, in the future when I write a macro. What do I need to do to keep this from happing again? Because the macros that I have written, others want to use them also. Is there something that I need to set so that they will work on other computers.
Thanks again...
2 ways I know of. I don't think there are more.
1. When you create a new macro, SolidWorks automatically includes the references for its own version as installed. So if you distribute your macros as text only, you won't have this issue. However, for someone to use the macro, they will have to go to Tools->Macro->New, paste your code, and save the macro.
2. Use late binding (google it if necessary) and don't include any references. Sucks for writing, but should work OK.
I haven't paid much attention on this issue but thought it has been fixed from SW2017?
what release are you using now?
I'm using 2015 now.
But we are about to go to 2017. I hope it's fixed to 2017.
You will most likely be updating your references again...after the update to 2017.
I'm not sure how this issue would be "fixed"... Unless 2017 has some sort of automatic reference checking and replacement feature I don't know of. It's a basic thing for VBA macros that applies whether you're running SW, Excel macros, etc.
Christian Chu wrote:
I haven't paid much attention on this issue but thought it has been fixed from SW2017?
what release are you using now?
Josh,
I'm not sure about this so I have my words in question mark
Unless there are some third party obj. lib such as Excel including in the macro, how hard to automatically update the SW obj. Lib. to the current version?
References have been hit or miss for me. When work upgraded from SW2014 to SW2016, all the references updated correctly. Unlike when going from SW2012 to SW2014 where I had to fix all references. Could it have something to do with the residue left behind when upgrading? When upgrading to SW2016 I used computer that never had SW2014 on it to resale all our macros.
This error is generally due to missing references. Make sure you've correct references in the macro. Update/correct the macro references to your SOLIDWORKS version as suggested here Fix-Update SOLIDWORKS Macro References? (don't worry on the fact that video is for fixing missing library error but check the process to update your macro library). Also uncheck the utilities library reference from the macro.