Gang...
There used to be a property that showed you parents files that were out of date or hadn't been opened after a child file was modified (Vault Status Modifier property). This property used to tell us when an .idw or parent file needed updated after a child had been edited. The property did work, but it looked the whole way down the structure and kind of lost what it meant. In other words, if you had a bolt ten levels deep it showed that every parent needed updated, including .iams, .ipn's , and .idw's all the way up to the top level. This meant that almost every file to the top level showed that it was out of date, which in fact, they were, but if you changed a bolt in a battleship, do you really need to update every file the whole way up? Technically yes, but is this being efficient.
I'm proposing to bring back this property, but only look at it's immediate children. In other words, if you have an .idw, the property would only look at the files that the .idw needs to update the views. It would NOT look at the structure the whole way down, JUST THE IMMEDIATE CHILDREN.
The problem is, that periodically we have users make a change to an .iam or .ipt and get side tracked or forget to open the .idw and these prints make it through the change process. This property would help find those .idw's that are older than the child check in dates.
Thank you,
Steve Hilvers