>>It would loose scope at this point. I just know this for sure, because I was bitten by this problem once. It was discussed here as well, but it was long time ago and I don't remember thread specifics. I recall, though, that Ed Rauh participated in it:)
>
>OK, I think it is starting to make sense to me, now.
>
>When I asked the parameter question in the discussion group of the framework I use (Visual Extend), I got an interesting alternative to your suggestion: instead of a private variable, I can use properties of the calling form, with ThisForm! The calling form would still be active in the DataEnvironment.OpenTables() event. At least, that was the claim.
>
>Hilmar.

That's a true statement too. At the point of form's Load _screen.ActiveForm refers to the calling form. I didn't think about it, because I usually have main program call a form. For two form situations this solution should also work. (haven't tested it though).