Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Welcome to the forum, Brian! Have you tried changing the sheet number to 1 for the INSERT_DRW_SHEET command? The admin guide is a little ambiguous about how it works.
Design well!
Tom -
Yep, I am forcing the regen on the model since I have NO_REGEN as I am passing paramter values into the model. Does not look like I can use this to do the same for the drawing. I also update the drawing views to no avail. Even when I manually do the process in Pro|E, the update of the views is not enough to make it think it has changed.
Geoff -
I have tried, 2 and also 1 to no avail with the insert sheet command. Just seems really odd to me that it fails, but it actually adds the sheet. Of course once it fails, the application stops.
Thanks for the responses fellows... If something else pops up that you might think of, let me know. In the meantime I will see what I can find out today.
I will say, the insertion of the 2nd sheet is enough to "trick" Pro|E to save the drawing. So my method will work, if I can find out why the comand is failing. Today I will attempt to insert a note and then delete it as a 2nd option.
Brian,
Try adding a REGEN_MDL REFDRW in between the Insert and Remove commands.
If the command set continues to fail, you should log this as a tech support ticket on our portal so that we can review it with you and find the proper solution.
Joel Beckley
Application Engineer
SIGMAXIM
Brian,
If the point is to let Creo know that the object is modified and ready for a save, try SET_MDL_MODIFIED.
This way there is no need to "trick" Creo.
Back in 2000, I didn't work here yet, my company had a similar problem with Pro/E (2000i I think?).
They started using a REG_CURVE, which was a small curve built into the startparts. At each regen it would vary in length, 20 to 25mm and back. Thus convincing Pro/E the part and drw has changed.
However, this has become a nussance in the new Creo, and it took a lot of programming to get rid of it. So I don't think it's a good solution...