Using Trail Files for Automation... barking up the wrong tree?

[dagarber]

Searching for info on trail files online I came across this post by looslib:

"[blue]The purpose of trail files is to allow you to rebuild a model after Pro/E crashes because of an illegal operation. They are not designed to be used to make similar parts to another design that someone just happens to have the trail file saved from.[/blue]"

I am trying to use a trail file to regenerate a ProE model from file without the user ever being involved... this allows a user without ProE knowledge to edit the text file and view the results (thanks to eDrawings without ever seeing the CAD interface... am I making a mistake trying to do this with a trail file? I want to develop something that is robust. Is using a trail file going to be something that I regret later on?

It seems like a really nifty thing to be able to do, but maybe its not the smartest way for me to go.

 

[JohnAndrews]

Using a trail file should work, but the part needs to be set up with Pro/Program to allow parameters to change. The trail file would then just open the part regenerate to activate Pro/Program, then use the Pro/Program option "Read File" to give the new parameter values, then it sounds like you would want the trail file to spit out the eDrawing.