Rename Reference Model 2

[treddie]

Hi all.

I have run into this before and at those times it wasn't any big deal, but now I have done it again and really DO need a solution this time. Otherwise, my workload just went way up.

Anyway, it goes like this. I have built a part and have published the geometry of it. Let's just call it Gizmo.prt. Then I created a new file called Gizmo_2.prt and copygeom'd the geometry from Gizmo.prt. I did this, so that I could easily preserve a history of the last part while making it easy to open up again if need be, without having to go through the trouble of "hiding" any later versions of it.

At this point, I created about ten saves of my work. So now I have Gizmo_2.prt.1 through Gizmo_2.prt.10. To make a long story short, I have a history of saved files done this way called Gizmo_2.prt through Gizmo_5.prt. BUT, it turns out that the gizmo is really only in files labeled Gizmo and Gizmo_2. All the other files from Gizmo_3 through Gizmo_5 SHOULD have been called Gizmo_Stringers and Gizmo_Stringers_2! So now I have a big problem...If I just rename the problem files via Windows as shown for all saves of the part, my old ref's to copygeom'd files are now missing. Creo can't find them because the file names have been changed.

My question is, is there a way in Creo to rename a referenced file without Creo rejecting the old references? After all, it's exactly the same file, just the name is changed, and the references are still the same. Is it possible to tell Creo to just accept a new ref'd file as the correct one, because after all, it IS the same file!

May the Creo Gods have mercy on my soul!!!

 

[robertib]

There is a way to do it.

Open all files that are referenced, and rename the problem files in session - be sure to include any drawings.

 

[treddie]

I wouldn't have thought of that one. That's a great idea! The only caveat is that you can't easily still save your file history, like prt.1, prt.2, prt.3, etc. I like to save those in case I make a huge mistake that requires me to roll back. The only way to do it would be to do what your saying for each most-recent file in the history, move it to a temp folder, then do it for the next-to-most-recent file, etc. But that is FAR less work than the alternative.

I will put that method in my list of procedures.

Thanks, robertlib!

 

[robertib]

Rename actually also renames the older files (as long as you do a rename rather than rename in session).

 

[mjcole]

Robertib: Good add on your secondary point the rename will update all the .# files in the directory.

Treddie: I've often saved copied the backup files to a folder called BAK for backups. Even on other systems that do not save previous files Catia for instance. Having to manually do a job proe/creo does for you is annoying. If an assembly is looking for a version with a specific name you could name rename your new file to update the reference using In Session or sometimes a Component Replace may work but not always.

I don't know if you used save as copy but just in case you do the currently active part is kept on screen after the save operation. You need to remember to open the copy file before you're actually working on it.

One good thing to note is that although you are not taken to the new file when performing save as copy and it cannot be found via In Session dialog it does get added to the File Menu's recent files list.

"It's not the size of the Forum that matters, It's the Quality of the Posts"

Michael Cole
Boston, MA
CSWP, CSWI, CSWTS
Follow me on !w¡#$%
@ TrajPar - @ mcSldWrx2008
= ProE = SolidWorks

 

[treddie]

Rename actually also renames the older files (as long as you do a rename rather than rename in session).

NO WAY! Then my prayers HAVE been answered in full! Looks like PTC was on it this time.
I see the Rename command now. So, when you say "in session" and NOT "in session", it doesn't look like you can turn off "In Session" in the radio buttons. Also, I imagine you would need to have any files open that reference the renamed files, correct? If so, do the copygeoms need to be set as "dependent" in order for proe/creo to recognize the associations?

mjcole> Thanks for the clarification. I knew about the Save a Copy thing, which has always frustrated me. It doesn't do anything any other program doesn't with Save-a-Copy, but I always interpret it to mean Save-And-Rename and find myself operating on the previous file when I should be working on the new one. I think those transistors in my brain are dead.

I saw a post once where a guy wanted to turn off the history trail because he was annoyed at having to constantly remove old files. Someone beat me to it, but I wanted to yell at him and tell him, "Do NOT do that." All it takes is one screw-up and you can turn a productive week into a redo-week at the drop of a hat without a part history.