×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

assy model is still referenceing older assy's that have had xrefs brok

assy model is still referenceing older assy's that have had xrefs brok

assy model is still referenceing older assy's that have had xrefs brok

(OP)
I have an assy model that is driving me nuts.  When I open it in sw2003, it wants to open all the files that have been made in the process of making this assembly.  Since every part in this assembly has "no" connection to any of those old parts I dont see why this is happening.  Every part I've checked by opening and listing external refs, and they are all broken.  the only reference to the old files is the top line of the external reference dialog box that says"Assembly:  c:\xxx\xxx\xxxx\xxx\oldfile.sldasm" but under it their are no features referenced any more because i have broken them.  The biggest problem with this is that at opening the file, I get 20 or more messages of "unable to locate the file c:\xxx\xxx\xxxx\oldfile.sldasm, would you like to find it yourself?"  I dont wantto find it it has no worth to this file, and should have no reference to it either.  Please help if possible.

RE: assy model is still referenceing older assy's that have had xrefs brok

I've noticed this happens sometimes after having used a join feature.  I have no explanation or solution.

RE: assy model is still referenceing older assy's that have had xrefs brok

I had something very similar a about 3 years ago. I had deleted a concept assy (or part) via Windows explorer without doing a "where used" in SW Explorer. I had forgotten that I had used the deleted assy in another assy & that created the type of messages you are getting.

I believe what I had to do was create a false assy of the same name & place it in the path specified. Then when the problem assy found it I simply deleted the offending assy from the current assy, resaved & the problem was gone.

from (the City of) Barrie, Ontario.

I tried sniffing Coke once, but the ice cubes got stuck in my nose

RE: assy model is still referenceing older assy's that have had xrefs brok

(OP)
Cor-Blimey-Limey-By making a "false assy" do you mean just start an assy and save it as the name that it was looking for, in the location it was looking for it?

RE: assy model is still referenceing older assy's that have had xrefs brok

I believe that's what I did ... it was several years ago & the memory cells ain't what they used to be ... not that they were that great to start with.

from (the City of) Barrie, Ontario.

I tried sniffing Coke once, but the ice cubes got stuck in my nose

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources