Hi Robert,
>> Ok. Understand....but this sound like a big "bug" and why only now we know this?
because other bugs with screens refreshing have lead to some differences in the way that the "parent" is understood and parsed. the root of the change (on my side) is in the AlertParent method in netweb.clw. It may be possible for you to override that to adjust to your situation.
>> all procedures are involved in a complex security module and procedure names are stored and used for access.
It's possible you could extend your security template to store a "procedure name" of it's own. Default this to the current procedure name, then that leaves you free to change the actual procedure name.
Bear in mind that only "containers" are affected by this. So you don't need to change the whole app at this stage.
As I say, this _may_ change in an upcoming build - but I need to review all the places where parent is set, and constructed, and that's a non-trivial task. I don't have the time to do it right now, but possibly in the not too distant future. So I recommend against wholesale changes to your system, but rather focus on container procedures where events may not be propagating.
cheers
Bruce