Working directory

[mprice214]

Hi all,

I'm having a problem with the way WF2 saves new assy's. I switch to a certain working directory during assy and part creation for example a project subfolder. When I create a new assy and begin to assemble components from other directories, if I haven't saved the assy prior to adding components, ProE will now save the newly created assy to whatever directory from which I pulled the component. As this was not the way ProE used to work, it proved to be very dangerous initially. Is this something I'm going to just have to live with?


Thanks.

 

[hfd36jtb]

mprice214,


I am assuming that you are not using Intralink? I have not used Pro/E for quite a while without Intralink, so I cannot be sure if the issue you are having is normal or not. I have to believe that the way it is saving is that way the file management is going to handle the files. If your intent is to create new assemblies using new part numbers for the components, then I would suggest setting it up the file structure manually before starting any projects.


John

 

[dojo]

add file_open_default_folder to your config.pro with 'working directory' selected from the drop down box, and it will always saev new parts and assemblies in your working folder


(got no pro here but if i recall correctly its the correct option)


Nick

 

[hfd36jtb]

dojo,


I think part of this issue is having duplicates of the files in multiple locations. Do you agree? I am probably reading too much into it, but I had that issue in the past.


John

 

[mprice214]

Thank you.

 

[dojo]

Well, I had the same problem as mprice described in the beginning with wildfire.


For example : You create a step file from you model/assy tp send to a client, not in your working directory but directly in your c:\ root. You continue modelling, create new parts, assemblies, you save all your work during lunchtime, close pro or crash, you start up again, switch to your working directory, want to open the newly created parts/assy's and they are not there. They are indeed in your root folder as you created the step there. The config option sorts this.


Concerning the file management without intralink. We are a design office who work for quit a few clients. Some projects are a white sheet of paper, others are integrating a interior in a industrial vehicle cab under develpment. The cab is also under development so your bound to receive file updates. One person in the office is responsible for pro (yep where small ... 8 people) and does all the datamanagement and Pro setup/config's (that'll be me btw) Our file structure is somewhat like this


Projects


client1


project 1 for client 1


input


output


project followup


pictures


cad work


client data


client data before xx/xx/xx


Every new file update from a client is automatically detached/downloaded in a subfolder 'date of today' under input. The previous data under client dat is then copied to the folder client data before xx/xx/xx and the new data is then extracted under client data.


cad work is automatically set as working directory. Only one search path per project is allowed and its ...cad work\client data. (Also see my post about different projects/clients/configs etc here [url]http://www.mcadcentral.com/proe/forum/forum_posts.asp?TID=29 978&KW=dojo[/url](last one)


This is a work around, but not very time consuming and it works. No other user has to break his head asking himself if he is working with the right files.


It's not possible to adapt Intralink or pdm or any other data management system as we are depending on the client.


greets


Nick

 

[hfd36jtb]

Nick,


I see how you do it, and I have done something similar in the past. I guess I'm spoiled to have Intralink take care of this stuff for me. When I get an update from a vendor, I import it into the workspace with a diffrerent name or something to keep the two separated.


Thanks for the explanation.


John

 

[hlf71]

set up option "override_store_back=yes and save_object_in_current=yes"

 

[Dell_Boy]

a word of warning

injudicious use of hlf71's suggestions will give you duplicate files all over the places. This is absolutely not the right way to run Pro/E on a day to day basis.

override_store_back by default should be set to NO. save object in current only comes into play when override is set to yes.


DB