Preventing duplication...

[samickguy15]

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????

 

[samickguy15]

Maybe this should be in Data Management???

 

[looslib]

There is nothing that will prevent someone from creating a new aprt with an existing part number. It is not even possible with Intralink or PDMlink. The data checks only come into play when the user tries to check the part into the data management system and then is informed that the part exists.


File structuring, either in Intralink or just on a disk, is key to avoiding duplicate parts and making it easy to find common ones. Files on disk can still be duplictated as the check is only on the active folder. In a PDM system, tye check is against the data abse which knows about all parts.

 

[Dell_Boy]

looslib is way off the mark with his reply.

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

 

[shamus]

How do you enter directory searc paths into your config.pro?
Shaun

 

[superdutynick]

This was coppied out my my config.pro for you. I like to keep my config nice and tidy, so I seperate out all of the options and group them together. You can add as many as you want. There is also a way to do it with a file where your config calls out a file and the file specifies your search paths. That has been discussed before on here.


Make sure you use the absolute address





!#####################
! Search Path Configs #
!#####################
!
search_path /local/netplot/std_pdm

 

[Dell_Boy]

Nick,

why do you say

Make sure you use the absolute address

then use an example of a relative path (with unix standard / instead of the windows standard \)


DB

 

[mcgowanp]

Best way to do that Shamus is just do it with the options window in Proe, Let proe do its ownhouse keeping with regards the config.pro


When he says absolute adress, he simply means use the right directory that the parts are in, not parent directories, Proe does not do a recursive search, it does not drill down.


Big word of advice - Listen to dell_boy he knows what hes talking about!!


Have fun

 

[mcgowanp]

Oh yeah smaickguy15, I installed proe into 2 companies that started using proe without a PDM, when they finally decided to install a PDM it was a night mare as they did not keep the file properly filed or number. If you are going to go to a PDM, which if you are not operating across a number of company sites and have a relatively small number of users (under 15) then it may not be worth it. There are others ways (less expensive) to control your files etc. I dont know your business so maybe you cant do without one.


The biggest lesson I learned doing these installs isto educated the users at the start about keeping all files in the right place, file names as per naming conventions, and any part parameters that are containing part info that goes on a drawing that you also want in a PDM, try and decide on them now and enter the info nowto make any future work a little less soul draining!!