My first idea on this, are you just saving or are you using the save as utility instead? If you are using the save as then check to make sure the "include all referenced components" box is not checked.
Other than that someone who has experienced this before may be able to chime in on some other issues that may cause what you are seeing.
I forgot to mention that - you're right, Paul. I was using the Save As feature.
But, I just checked and the "Include all referenced components" box was unchecked, as you have shown. I will make sure that it will continue to be unchecked.
Thank you for your input.
But, I am still at a loss.
No answer yet, only questions..
Did you pack and go the original assembly?
Are the files coming up as read only or is SW giving you the option to save over read only files?
When you do a save as, are there other popup window showing up?
Are your options set when you add a new part to automatically save to the folder it was created from?
I have some answers to your questions.
Yes, I went back to the original assembly after I deleted the part files. Then, SW was at a loss as to where to find the files. It was looking for them in my directory, but I had deleted them, you see - so I had to direct SW to find them on the Engineering Drive, where they are supposed to be.
I'm not sure what pack and go means.
The part files were not coming up as read-only. They were writable.
When I did a save as, there were no popup windows showing up, other than every once in awhile, asking me if I wanted to save the assembly, and one of the parts.
I'm not sure about your last question. I don't think it's set to automatically save to the folder it was created from.
Thank you for your help.
Pack and go is one of the best and in most cases safest way to transfer assemblies from one design frame to another.
It breaks all constraints and ties to the original assembly. If you are re-using an assembly and changing said assembly from the original it is the only way to make a copy of your assemblies without wreaking havoc on your file structures.