Assuming that you're going to create a persistant object reference to the calling form using a property, you will not be able to destroy that form with that object reference in place. IOW: the calling form cannot be released until you set the property on the new form to .NULL.

That's one thing I can think of, right now.

>I have quite a few instances where I call a form from another form and the called form needs access to some of the properties and/or control values of the calling form. I have decided to just pass one parameter to the called form, an object reference to the calling form, rather than sending the multiple values the called form needs.
>
>Is there a downside to doing this? Is this a good way to do this?
>
>Thanks,
>Paul