I found it so slow, that I preferred to create my own which uses an index.
And with time I added a lot of other functions
- batch rename
- Batch rename from Excel
- Batch print
- Bach export
- …
Use this quite often. Works Great. I like it far better than Solidworks explorer.
Its faster, and has more options. and Joel is very helpful in its use, and adding even more functionality.
Working on 1000 parts import for a few weeks.
Looks like customer did it in multibody. We get a weldment and a machined assembly.
Import result in 2 part files.
Saving the bodies out give import1.sldprt to import1000.sldprt
So I use PnG to change all the filenames so they don’t replace each other.
Some features are only 5% implemented.
I rarely use SWx Explorer. When I do, it is an open-ended task that takes as long as needed, because it’s so slow.
My files are stored on a network space. Would SWx Explorer find Where Used faster if I ran this upon the server instead of my client workstation?
Thanks.
Bookmarked, thanks for posting!
Did I find a failing of Solidworks Explorer, or am I doing it wrong?
Somehow, sometime, someone (probably me, duh) duplicated a file into a new subdirectory in my library. It is used incredibly commonly in my work, tee.SLDPRT , a socketweld tee pipe fitting. I wanted to know where THIS file was used so that I can remove references to it and replace them if needed with the proper component. I believe this is not what I got in return. I think that it is returning every assembly or derived part which contains a reference to a file with this same name, but not THIS redundant file in this location.
That is, it shows me Where Used for both this bad one and the other, properly developed and stored file of the exact same name. The results are indistinguishable.
It is also returning, in the case of one derived part, components where this was used and then its reference was broken. What’s the point of breaking this reference when it still finds it in a search for where used? I am so confused.
Does seem like it’s just a limitation of the program. Unless you can query by something that makes that part unique, I think its probably not going to help you find those needles in the proverbial haystack.
Maybe this is your saving grace. Provided both parts are identical copies, why not delete the copy (Ok…move and rename it for safe keeping), then do a rename on the original and let it find everything and update. Then rename it back. Seems like this would “update” all of the broken references to the second copy we just deleted.
Yeah, I don’t get why the reference is still left in place when you break it. I get leaving a history in the file but not the actual reference. Pack n Go does ignore it but Rename does not.
So I updated to 2020 SP.5 yesterday, and lo and behold its missing a primary function for renaming assemblies with virtual components. Originally in 2019 SP.5 - there was a “search” button: you would check the box “include virtual components” , hit the “search” button - it would populate those items, then you could rename your assembly successfully.
Now if you just check the box - there is not a search function - and as I expected after a test - the references of those virtual components do not update and reference the new name 
If anyone still has 2019 - they can probably verify the button I’m describing.
Yeah, you can tell they redesigned the dialogue, a lot of little changes.
Yeah, that’s the one. What a pain this is going to turn out to be… probably see it back in release 2022 SP.5…
Per the VAR: There is an open SPR for the issue…
“SPR 1194201: Virtual Component external references status becomes out of context after parent assembly is renamed”
Update..
My work-around so far is this:
Open drawing referencing the assembly you want to rename- open the assembly and rename it using “save as” with references.
Go to File > open > click on any other drawings that file is referenced in. Click on “references” in lower pane.
Double click on where the original file name is referenced and replace with the newly named file by browsing to it and selecting it from the list.
Delete the original after it’s been replaced in all “where used” instances..
<()>
I was looking for SolidWorks Explorer (me too I feel the need for it every 5 years), and discovered it was dead for a long time…
Threehouse would be a nice place to implement the lost functionality. It almost does, as you can rename files and edit it’s properties (not always but I don’t want to loose time on this), but it’s only for display purposes - it does not touch the files.
Again, very little foresight from DS.
I never used SW eXplorer, it was on it’s way out as we started with SW. But if it were at all like Solid Edge’s Revision/Design Manager, then removing it would cripple a substantial part of the user base. It was a Move Tree, Copy Tree, mass data card editor, part swapper, Swiss Army Knife of SE file reference and attribute management. Any other users of Design Manager with Solid Edge?
You still have the right click menus for “Rename, Replace, Move…etc.” That is all that is left of SW Explorer, now called “File Utilities” in the installer. The treehouse enhancement to take over the property editing would be nice…I’d prefer a table view though.