Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

You're a saint—thank you!

 

The solution I’ve come up with so far avoids interacting with the resolve-file dialog entirely. Instead, I run a macro that replaces all parts with missing references (ActiveDocument.File.ReferencedFileDescriptors.ReferenceMissing).

 

What it essentially does is loop through every file in the active assembly (or drawing for that matter, if I set the FileReference as ReferencedObjects(1)) and check if the file has a reference. If it doesn’t, it replaces it; otherwise, it moves to the next file.

 

I’ll look into the PDF and the event you mentioned—thank you again.

 

You guessed right that I’m still fairly new to VBA. I didn’t realize it was so… “frowned upon,” it seems. Besides VB.NET being newer, are there any other major differences from VBA? I’ll make sure to dive deeper into it.

 

edit:

would you be interested in the code at all? (is it normal in this forum that if somebody has come up with his own solution that the code is posted as a solution?)