Steve_Stafford
2004-08-11, 11:36 PM
We have been borrowing elements primarily (instead of worksets themselves) for some time now. It works very well.
One side effect of this practice is the occasional need to save a second time. The first time all worksets and borrowed items are checked to be relinquished and the local file checked to save as well. Yet, closing the project at this point generates a Save to ...relinquish and save...don't save dialog box. If you cancel and start a second STC you find borrowed items is "checkable". So you check it, save local too and you're good to go.
Forgive me if this is in the Workset doc's somewhere but I've not noticed it yet. I'd love some "factory" insight into why it is necessary to do this. It seems to me, if a STC forces Revit to need a second STC to turn in those borrowed items, this second try could just be part of the first and hidden from our users. Either way a solid reason would go a long to making new users less nervous about process.
Thanks!
(new users...STC is "Save to Central")
One side effect of this practice is the occasional need to save a second time. The first time all worksets and borrowed items are checked to be relinquished and the local file checked to save as well. Yet, closing the project at this point generates a Save to ...relinquish and save...don't save dialog box. If you cancel and start a second STC you find borrowed items is "checkable". So you check it, save local too and you're good to go.
Forgive me if this is in the Workset doc's somewhere but I've not noticed it yet. I'd love some "factory" insight into why it is necessary to do this. It seems to me, if a STC forces Revit to need a second STC to turn in those borrowed items, this second try could just be part of the first and hidden from our users. Either way a solid reason would go a long to making new users less nervous about process.
Thanks!
(new users...STC is "Save to Central")