Macro throwing error

[AlexLachance]

I have a macro which we use to select the level at which a note will grab the property and it's not working anymore, it throws an error 91, object variable not set.

image.png (31.04 KiB) Viewed 1605 times

Could anyone help me? I've attached the macro, I'm sure it's something silly.

Basically, we link a note to a part/assembly and then use the macro to select the desired level to pick the property from. When we try to select the desired level, the error appears.

[AlexB]

Are you able to give a list of steps that causes it to fail and show what line it breaks on by clicking Debug?

[SPerman]

My guess, is that your index is wrong here. (i.e. the value for NumSels doesn't match the allowed values. You told it to grab #3 when there are only 2.)

Select Case swSelMgr.GetSelectedObjectType3(NumSels, -1)

[AlexLachance]

Are you able to give a list of steps that causes it to fail and show what line it breaks on by clicking Debug?

Selecting a note, clicking on the macro and trying to select the level from the pop-up window was throwing the error, but it isn't throwing an error as of right now... Seems like it was a case of "Restart the darned program"

[Stefan Sterk]

I believe the selected component is Ligthweight, which will throw an error when pulling the custom properties.

[AlexLachance]

I believe the selected component is Ligthweight, which will throw an error when pulling the custom properties.

I will validate the next time my collegue gets the error, thanks Stefan!

[josh]

Hey, I think I recognize that form...

Yep, if it happens again, definitely hit "debug" and show which line gets highlighted. If we're lucky the VBA debugger will actually hightlight the problem line.

[SPerman]

If you aren't familiar with the VBA debugger, you should be. It is easy to learn and will be invaluable in sorting these types of issues.

https://www.myonlinetraininghub.com/debugging-vba-code

[AlexB]

@AlexLachance If you add this code to the location shown in the image, it should solve what @Stefan Sterk was talking about.

Code: Select all

Dim suppression As Integer
suppression = myComp.GetSuppression
If suppression = swComponentLightweight Then
    myComp.SetSuppression2 (swComponentFullyResolved)
End If

Alternatively, the updated SWP file is attached.

[AlexLachance]

Hey, I think I recognize that form...

Yep, if it happens again, definitely hit "debug" and show which line gets highlighted. If we're lucky the VBA debugger will actually hightlight the problem line.

I think you were the one that developed it for us

I did hit it but I wasn't quite understanding what I was being presented with. I believe it was in this general area, at "first get overall document properties" that was getting highlighted.

Thanks @AlexB for the little tweak, will give it a go! If I get more macro errors, I will definetly try adding a screenshot of the debugger next time.