Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
If a user makes some changes after backing up a part/assembly in proe and then save the model, the changes are saved in back up directory i.e the working directory is changed. Requirement is that if a user creates a part and takes a backup, then only upto that much part should be saved in backup directory and further changes to be stored in original working directory.Please help.
I have experienced this issues as well. It doesn't only happen when you save a copy but also when you open a file that is not in the working directory. Like if you start a new part and specify a startpart from a different folder. The new file is saved in that folder instead of the working directory. This does not happen if you use the default startpart specified in your config.pro file. It only happens if you manually specify a different one.
I guess the only suggestion I have for you is that you create a mapkey for "save a copy" that resets the working directory after the save as function.
If you are working in a Pro/E session linked to a PDM workspace this is not an issue.
Paul,
try config.pro option file_open_default_folder working_directory to force ProE to stay in working directory.
Martin
I'll give that a try. But, no matter what that help document says if you set a working directory it should always save there, no matter where you open from or save as to. But, that is just my oppinion.
Thanks for the pointer.
Tushar,
backup command works as specified on http://www.ptc.com/cs/help/proengineer_hc/proe_help/ ...
...
If you make changes to a model after backing it up and then save the model, the changes are always saved in the backup directory
...
Martin
Yes, that is what they have mentioned in their help document.
However, i agree with Paul that once I select a directory, it should always save there no matter where I create it's backup.
Thanks anyways to all of you for replying.
Got the solution friends...
changed config option "override_store_back" to "yes"