Multiple copies...

[samickguy15]

I'm sure admin will probably delete one of these posts, hopefully not this one, since I think it belongs here more appropriately...


We're migrating from SW into Pro-E currently and don't have a dedicated server in place yet. The issue right now is not creating duplicates of existing models. Is there a code that can be put in to config.pro or something that won't allow the same file name in a directory to be used more than once. So for example...


We already have this file...


R:\Pro-E\87443458.prt.1


I don't want anybody to be able to create another 87443458.prt in that directory. So when the new part/drawing/etc. box shows up, when they click ok to start the part I want an error to show up. Is that possible???


I understand that there's ways to keep from saving multiple copies, but it's wasteful to model the same part twice just to realize there's already another copy. It's also rather time consuming to search for each part before moving on.


Any suggestions????

 

[Dell_Boy]

If a particular part is in session, Pro/E will NOT allow you to create another part with a duplicate name.

If a particular part is in the current folder, Pro/E will NOT allow you to create another part with a duplicate name.

If
a particular part or instance is available via your loaded search paths
and you try to duplicate its name, Pro/E will warn you about it and ask
if you want to continue.

First
and foremost, I would recommend implementing a structured naming and
filing system and build a proper library for your common components. If these are done correctly, it should make everyone's life easier.

A possible workaround would be to put ALL
your component folders on search path so you at least get warning of
duplication. An added benefit of this would be that if you want to
assemble an 87443458, you just type that into the dialog box and Pro/E
will always find it for you. If you want to Open an 87443458, again just enter
it and the .prt or .asm extension and again Pro/E will always find it for you.

Last
time I looked SW could not do this so you probably wouldn't know about
it or how fast and useful it is especially for directly retrieving
instances (configurations)


DB






Edited by: Dell_Boy

 

[jnoval]

Bye PdmLink and your naming probling is over. I think it also work for SW.

 

[jnoval]

Sorry I of course should have write:


Purchase PdmLink.