I see what you mean - I was thinking in terms of a form class which was being used strictly for this kind of modal lookups/data entry. I have one for Memo field editing, but because it is used in a very narrow area I don't need to worry about the items you mentioned.

Thanks,
Barbara
>
>Do you mean, pass the calling object to the called object, and have the called populate a property in the calling?
>
>You could, but I woudln't want to.
>
>If you aren't calling from an object (like a PRG), you'll need to create one anyways, making how it works inconsitant from call to call. On top of that, you are tightly coupling the functionality to the UI now.
>
>You can't easily tell wether or not the called form was OKed or Canceled without another property in this case, and you can't easily validate and accept the calling forms property in the calling form because it was already populated by the called object.
>
>A 3rd parameter object is best, IMO, if you're gonna do it this way. But I still prefer the "Hide() instead of Release()" method.