Skip to main content
C
CarrieIves1-Visitor
1-Visitor
January 6, 2014
Question

References lost when files copied to a new folder

  • January 6, 2014
  • 1 reply
  • 2971 views

I am working with a co-worker who is in a different physical location. We have structured our assembly this way:

Top level.asm

His assy.asm

My assy.asm

I sent him a copy of one of the sub-assemblies in my assy. When he opened it, the mates were failing. (These were just mate and aligns with some offset distances, nothing complicated.) Any ideas what's going on?

We are using Wildfire 5/Creo Elements. I am using date code M180. He is using Wildfire 5, date code M060.


Thanks,

Carrie


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

D
dschenken1-Visitor
1-Visitor
January 6, 2014

If he has different items with the same names in the folder than you have, that would be a source of this difficulty.

To be certain, create a backup of your assembly - this will place copies of all the parts and assemblies into one folder. Send that. Have him place the contents in it's own folder and remove any search paths from his config. Then he can set his working directory to that directory and tryopening the assembly.

If it works, and it should, then it's a matter of tracking down parts that are not the same, but have been given the same name.

An experience of mine was similar when two different workers called an item Plate. Depending on which Plate got opened, one of the sub-assemblies would fail, having gotten the wrong Plate. This is the reason for Intralink and PDMLink; to prevent same-name, different item conflicts.

It could also be that he has the correct files, but old versions.

Terms & ConditionsAccessibility statement