18 Replies Latest reply on Jan 5, 2018 3:20 AM by Ivana Kolin

Update to Office 2013 has VBA code not working

Will Speaker Dec 28, 2017 10:43 PM

I'm using VBA to change property fields in a drawing. I just upgraded my computer which is now running Office 2013 and my code doesn't work anymore. I get an error message of "Compile error: Can't find project or library" when I try to execute the following code. Additionally, the text "swCustomInfoText" is highlighted by the debugging program.

Sub ChangeProperties()

Dim swApp, Part As Object

Dim boolstatus, retval As Boolean

Dim swModel As SldWorks.ModelDoc2

Set swApp = CreateObject("sldworks.application")

swApp.Visible = True

FilePath = DirectoryPath & "\" & DrawingFileName

swApp.OpenDoc FilePath, 3

Set Part = swApp.ActiveDoc

retval = Part.DeleteCustomInfo2("", "DrawnDate")

retval = Part.AddCustomInfo3("Default", "DrawnDate", swCustomInfoText, VBA.Format(VBA.Date, "m/d/yy"))

boolstatus = Part.EditRebuild3()

End Sub

Re: Update to Office 2013 has VBA code not working

Solid Air Dec 28, 2017 11:32 PM (in response to Will Speaker)

Sounds like some of your SW references are missing. See if your macro is referencing SOLIDWORKS (version) Constant type library.
Like Show 2 Likes(2)

Actions
Re: Update to Office 2013 has VBA code not working

Deepak Gupta Dec 29, 2017 7:59 AM (in response to Will Speaker)

Start a new macro and copy paste these codes.

Option Explicit

Dim swApp          As SldWorks.SldWorks
Dim swModel        As SldWorks.ModelDoc2
Dim swCustProp      As CustomPropertyManager

Sub ChangeProperties()

Set swApp = CreateObject("sldworks.application")
swApp.Visible = True

FilePath = DirectoryPath & "\" & DrawingFileName
swApp.OpenDoc FilePath, 3

Set swModel = swApp.ActiveDoc
Set swCustProp = swModel.Extension.CustomPropertyManager("")
swCustProp.Add3 "DrawnDate", swCustomInfoText, VBA.Format(VBA.Date, "m/d/yy"), 1
swModel.EditRebuild3

End Sub
Like Show 1 Likes(1)

Actions
- Re: Update to Office 2013 has VBA code not working
  
  Will Speaker Dec 30, 2017 5:58 AM (in response to Deepak Gupta)
  
  Thank you for taking the time to respond. However, this did not work. The program balked at the command line "Option Explicit"
  
  so I eliminated "Option Explicit" from the code and the following error generated.
  
  Any suggestions? Again, I just loaded the Office 2013. My code had previously worked on other computers running Office 2013, but I wonder if there have been any changes to Office 2013 that is affecting the code.
  
  Like Show 1 Likes(1)
  
  Actions
  - Re: Update to Office 2013 has VBA code not working
    
    JOHN GEORGE Dec 30, 2017 7:36 AM (in response to Will Speaker)
    
    Will,
    Have you tried Property Tab Builder instead of macro
    It's right on the task pane and can select the date you prefer
    
    Like Show 1 Likes(1)
    
    Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Solid Air Dec 30, 2017 7:51 AM (in response to Will Speaker)
    
    If possible, please upload your excel workbook. If you cannot do that then in VBA go to Tools, Referenceces and post a screen shot of the references - VBAProject window so we can see if you are missing any SW references. I am concerned that Option Explicit generated an error; something I have not seen.
    
    Like Show 2 Likes(2)
    
    Actions
    - Re: Update to Office 2013 has VBA code not working
      
      Deepak Gupta Dec 31, 2017 6:18 AM (in response to Solid Air)
      
      Solid Air wrote:
      
      I am concerned that Option Explicit generated an error; something I have not seen.
      The error is due to fact that option explicit is inside the sub/procedure which I believe is not correct.
      
      Like Show 1 Likes(1)
      
      Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Rob Edwards Dec 30, 2017 10:41 AM (in response to Will Speaker)
    
    Hi Will
    Option Explicit has to appear at the top of your code
    
    Like Show 2 Likes(2)
    
    Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Amen Allah Jlili Dec 30, 2017 2:38 PM (in response to Will Speaker)
    
    It will keep doing that because you are not references the SOLIDWORKS tlb.
    Remove the Option Explicit
    And try this:
    
    Sub ChangeProperties()
    Dim swApp, Part As Object
    Dim boolstatus, retval As Boolean
    Set swApp = CreateObject("sldworks.application")
    swApp.Visible = True
    Dim FilePath As String
    FilePath = DirectoryPath & "\" & DrawingFileName
    swApp.OpenDoc FilePath, 3
    Set Part = swApp.ActiveDoc
    retval = Part.DeleteCustomInfo2("", "DrawnDate")
    retval = Part.AddCustomInfo3("Default", "DrawnDate", 30, VBA.Format(VBA.Date, "m/d/yy"))
    boolstatus = Part.EditRebuild3()
    End Sub
    
    Cheers,
    Amen
    www.cadsharp.com
    
    Like Show 1 Likes(1)
    
    Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Deepak Gupta Dec 31, 2017 6:17 AM (in response to Will Speaker)
    
    Like Solid Air mentioned, are running the macro from Excel file? If yes then you need to set reference to SOLIDWORKS libraries.
    
    And like Rob Edwards mentioned, Option Explicit should be out of Sub and not inside it.
    
    Like Show 2 Likes(2)
    
    Actions
Re: Update to Office 2013 has VBA code not working

Amen Allah Jlili Dec 29, 2017 6:40 PM (in response to Will Speaker)

Will,

Either you use the right libraries (Go to references and make sure than sldworks object types and the swconst tlb checked) or you can use late binding. Using late binding deprives you from intellisense on one hand but in the other hand, it lets SOLIDWORKS figure out the types during runtime (So no need of adding those references).

To use late binding,

Remove this
Dim swModel As SldWorks.ModelDoc2

and change swCustomInfoText to 30

Cheers,
Amen
SolidWorks API Training and Services
Like Show 2 Likes(2)

Actions
Re: Update to Office 2013 has VBA code not working

Ivana Kolin Dec 30, 2017 1:30 PM (in response to Will Speaker)

can you post here your references?
Like Show 2 Likes(2)

Actions
Re: Update to Office 2013 has VBA code not working

Will Speaker Jan 4, 2018 2:24 PM (in response to Will Speaker)

Thank you to everyone who pitched in to solve my problem. My program was fixed by replacing swCustomInfoText with 30. I sincerely appreciate the help!
Like Show 1 Likes(1)

Actions
- Re: Update to Office 2013 has VBA code not working
  
  Amen Allah Jlili Jan 4, 2018 2:27 PM (in response to Will Speaker)
  
  There you go buddy! You should always listen to me
  
  Cheers,
  Amen
  SolidWorks API Training & Services
  
  Like Show 1 Likes(1)
  
  Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Will Speaker Jan 4, 2018 5:27 PM (in response to Amen Allah Jlili)
    
    Like Show 1 Likes(1)
    
    Actions
- Re: Update to Office 2013 has VBA code not working
  
  Solid Air Jan 4, 2018 2:55 PM (in response to Will Speaker)
  
  Will, still would have been nice if you would have posted a screen shot of your references. Code is much easier to read with swCustomInfoText than just 30 (means you need to spend more time researching what it means).
  
  Like Show 1 Likes(1)
  
  Actions
  - Re: Update to Office 2013 has VBA code not working
    
    Will Speaker Jan 4, 2018 5:35 PM (in response to Solid Air)
    
    I did not have the SW utilities 2015 type library selected. I had all others that you show. I'm guessing that my previous code would have worked just fine with the new reference addition. I added it just in case I might need it in the future. Thank you very much for you help!
    
    Like Show 1 Likes(1)
    
    Actions
    - Re: Update to Office 2013 has VBA code not working
      
      Solid Air Jan 4, 2018 6:36 PM (in response to Will Speaker)
      
      Normally it is the constants library so I am not sure what the issue could be (unless even though it is checked, excel is not finding that reference).
      
      Like Show 1 Likes(1)
      
      Actions
- Re: Update to Office 2013 has VBA code not working
  
  Ivana Kolin Jan 5, 2018 3:20 AM (in response to Will Speaker)
  
  I would like to see your references anyway. Or I don't need to see it. In your case is or reference to Solidworks <xxx> constants type library not checked or there is above this library a "missing" library checked - probably previous office version? In case of unchecked library, find it in list and check, in case of missing library, uncheck it.
  
  Like Show 2 Likes(2)
  
  Actions

Go to original post