I am sick of closing SW when migrating/combining manually and over righting files with the same name, etc.
I'm not familiar with whether it is currently possible. If it is not it could be a good enhancement request.
Jeff, I have tried ER a few years in a row now. Not possible now to my knowledge, but I would think a simple script or new option could handle it. Hoping to get some traction. Maybe there is a flaw in what I am doing? IDK. Dave
David Antanavige wrote:Jeff, I have tried ER a few years in a row now. Not possible now to my knowledge, but I would think a simple script or new option could handle it. Hoping to get some traction. Maybe there is a flaw in what I am doing? IDK. Dave
David Antanavige wrote:
The closest thing to what you are asking for is probably the SWX Rx. I run this frequently and especially if I am having ANY problems. I don't know if it helps, but it cannot hurt. Perhaps SWX can give us such a cache clearing tool. It would make sense to include it in the Rx.
Have you requested this with an Enhancement Request? If so then post its number here so we can all vote for it. More votes really does get their attention.
Good call, as usual. I went back and checked and added the ER. #1-17911372755.
David Antanavige wrote: Jeff, I have tried ER a few years in a row now. Not possible now to my knowledge, but I would think a simple script or new option could handle it. Hoping to get some traction. Maybe there is a flaw in what I am doing? IDK. Dave
Can you explain a bit more what such a button would do? Is it related to PDM, or just SolidWorks? Can you describe a situation where you would need that button?
Ok so here is the situation, and it is not common and not necessarily in line with best practices. Once in a while I will have to combine data from various into one major assembly, example: 3 different parties are working on sets of the same model and then you need to recombine/over write/ fix references. When you open an assembly the parts that are resolved will have their specific file references and once you close the assembly those references are remembered. So if I go to open an assembly with some of the same file names involved from a different location it will point back to the original location. Obviously there is a bigger issue with how the data is being managed and shared, but when I have something like this going on it slows me down pretty hard. In ProE they had a tool where you could just clear out your local cache, this would cause it to drop all names and references used as if you had just opened the software. You could essentially remake "Part1" forever. Does this make sense?
To start, I would try to only have one copy of things for everyone to work on. There are ways to make that work. It sounds like you need to know which is the correct file for each thing. If I were doing something like this, I would open the version of each part that I wanted (and leave them open) and then open the assembly. The assembly will use what is open. You can then save the assembly and it should be looking at the directory location for the parts you had open when you saved it.
It sounds to me that you are referring to "Erase not displayed" in Pro/E. If you are, then it doesn't really drop the names and references. If that isn't what you are referring to, can you please be more clear?
Do you use "Find References" in SolidWorks to double check what is being looked at? When you have the assembly that you want, do a Pack and Go to the directory you want everything in and that will have all the references to the files in that directory.
Have you used "Reload" in SolidWorks, it may help a few things.
Thanks for the info. As I mentioned this is a special case, normally everything would be on my vault. Unfortunately I was not involved with this model until cleanup time came around. I do use SW File References and I leverage them when doing this kind of work. The problem arrives when I am looking at several versions of the same file from different users/locations. I can change the references before opening assemblies or open the file first as you say, but if I close that file and want to pull the same file from a different location I run into issues. I need to close everything and SW and basically start again.It has been a while since I used Pro E so I do not recall the specific function, but it essentially cleared all the data in way that achieved what I need here.
I am doing some research into the "reload" command per your suggestion, let me know if you think of anything else that could help.
David, now that I have a better understanding of what you want to do please consider the following recommendation. Let go of the mentality to "essentially remake "Part1" forever." You are already experiencing problems with this and it really is asking for trouble. There isn't time to describe the problems we had before PDM when we had the same part name in multiple locations. Can you say MAJOR HEADACHE?
For new parts you will avoid a ton of problems if you get in the habit of giving them new and unique names from the get-go. Even if it is a temporary part file give it a name like Temp-x where x is the next available integer. Since you do have others in your company working on SWX you would be well served to keep these files on the network, perhaps in a project folder and even add a project identifier prefix to the part files until you turn it into an official part with its official part number.
If at all possible you should start using the SWX PDM.
When I read your original post I understood it to refer to the actual computer cache. I know that ACRUD used to have a real problem not letting go of memory and we would shut it down and even reboot our machines a couple of times a day. I thought you were referring to a SWX problem similar to that.
Well, there's this, but it is specific to PDM:
Here are a couple of ways to do it with a macro:
Is there a way to clear memory in SolidWorks when building assemblies with API
And just for information:
SOLIDWORKS low resources – What’s holding my RAM hostage? | Computer Aided Technology
Thanks for the info. I use PDM here and this is a special case and the files are not on the vault. That feature does not quite do what I am looking for, while it is awesome for clearing out your storage. I think the API info you shared is promising, i figured API is the way to go, I am just a newb in that realm and need to do more homework. Thanks for the added info on RAM as well, I have a co worker who will benefit from that.
Retrieving data ...