Thanks Michael -

This is a horribly designed view - well, parts system in general. You have to find a child, then go from there to the parent so you can create a new child. The entire parts module needs a rewrite, but that's not in the cards at this juncture. As another example, it uses DD code to get the parent part # & then procedural code to create the child.

We've dealt with it, but doing so made me think that Key_Field_State might be augmented to reset the field to its original value.