cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

prevent working with a higher release

dvarkevisser
1-Visitor

prevent working with a higher release

Dear all,

I am asked to find a solution for a problem:

Company is working with 8 engineers on different projects for different clients, by default people work with WF3. One client wants his project done in WF1 because thats the release they are working with (and they dont want to upgrade yet). This is no problem. Every project has its own directory thats completely separate from other directories.

Problem: on a couple occasions the WF1-client'swork is opend and saved with WF3 by mistake, work cannot be converted to WF1, backup has to be used and lots of work is lost.

How can this be prevented? Is it possible to forbit directories becoming working-directories in a certain version of Pro/engineer??

Kind regards,

Dennis Varkevisser

______________________________________________
Dennis Varkevisser
Flexible Engineering Support
<u>www.flexibleengineeringsupport.nl
+31 6 50 68 01 79
</u>
2 REPLIES 2

We have a start up script that we've developed where the user picks the
client they are working for. This sets a certain trail file to run
which runs a mapkey that loads a client specific config file, setting
the right start part, formats and any other config settings the client
wants us to run. We've toyed with setting the version of Pro|E in the
start up script as well, so if you pick client A, it'll launch WF1 even
if you've double clicked the icon for WF4. We haven't implemented it
yet, though.

This doesn't solve the problem of a user working away for client B in
WF4 and then switching to client A's work without restarting Pro|E. I'm
not sure there's an easy way to fix that problem.

Doug Schaefer
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
FV
17-Peridot
17-Peridot
(To:dvarkevisser)

Hello all,

Dennis,

If you have Pro/Toolkit look up 'ProDirectoryChangePostAction' help section.

Alternatively, using jlink ,look up 'pfcSession.SessionActionListener.OnAfterDirectoryChange'

Another option is to close pro/e session if a user hadwondered into a wrong directory. To do this you could make a short batch/script file to run at Pro/E startup. Use 'FINDSTR' or 'grep' to extract fobidden directory names from the latest trail file and 'TASKKILL' or 'kill' depending on OSto close pro/e sesion.

HIH.

Feliks.



In Reply to Dennis Varkevisser:

Dear all,

I am asked to find a solution for a problem:

Company is working with 8 engineers on different projects for different clients, by default people work with WF3. One client wants his project done in WF1 because thats the release they are working with (and they dont want to upgrade yet). This is no problem. Every project has its own directory thats completely separate from other directories.

Problem: on a couple occasions the WF1-client'swork is opend and saved with WF3 by mistake, work cannot be converted to WF1, backup has to be used and lots of work is lost.

How can this be prevented? Is it possible to forbit directories becoming working-directories in a certain version of Pro/engineer??

Kind regards,

Dennis Varkevisser

______________________________________________
Dennis Varkevisser
Flexible Engineering Support
<u>www.flexibleengineeringsupport.nl
+31 6 50 68 01 79
</u>
Announcements


Top Tags