This is the third time today I've tried to get SW to update an assembly. I deleted an old component and inserted/mated a new sub-assembly (similar parts but no common file names to confuse it). I save the assembly and close it and the next time I go to open it get the message "internal ID doesn't match". I've checked that the references are pointing to the correct directory for the new subassembly. I've verified there isn't a file with the same name in the directory where the upper assembly reside. I can open the subassembly and then the upper assembly and still get the same message. The last time I told it don't use the version of the subassembly that had the mis=match ID, inserted a new copy, and then it magically decided to re-insert some additional copies!
What (if anything) can you do to get SW to actually update a file when you make a change?
Gregory,
I suspect that you have another file of the same name in another directory and SW is finding that file first, because the file you want is not in the first place that SW is looking. Do you have SW look in particular directories first? If so, it is probably in one that gets searched before the one that you are expecting. If you don't, then SW has its own priority for which directories get searched first.
If you do File/Find References when it has the "wrong" file in the assembly you should see where it is coming from.
I don't remember how SW decides where to search first (except that anything in memory is assumed to be correct), can't think of the magic incantation that will find the sequence in Help, and don't have access to SW for the next week or so.
Jerry Steiger