Ok, when i get some time I will probably do some experimenting with this to determine the exact cause so it can be avoided in the future. I did not realize that the "this" reference in the ShowDialog() method is the default so is not needed. I will change these calls appropriately.

opOptions is an instantiated object holding the options parameters. The idea was to pass the object in, perform any modifications and update the "master" object. I also suspect this is where the issue lies and I will experiment with this when I get a chance. The basic methodology was taken from an example in the Help so I will revisit this ans examine it. Thanks again for the input.

Bill

>Bill,
>
>There's nothing wrong with doing any of the things you did ... but it may have been the combination of two or three of those things that caused problems.
>
>Here's some more info (sorry that I didn't elaborate more in my first post):
>
>The .ShowDialog(this) is redundant, since "this" is the default.
>
>I think possibly what caused the problem though was setting this.opOptions = frmOptions.opOptions ... is opOptions an object or simply a string? If it was an object, then this.opOptions would be actually referencing frmOptions.opOptions instead of just taking it's value and then I'm not sure if frmOptions.Dispose() would be able to dispose of the form because of that reference.
>
>Also, are you actually doing something in the dialog with opOptions? I just wondered why you passed it as a parameter and *also* set it again after you were done with the dialog.
>
>But, anyway, you redesigned it and now it works, so that's all that matters. <s>
>
>>>Most of my time is spent in ASP.NET and have only limited experience in .NET Win forms at this point so I'm still navigating the learning curve there.<
>
>I'm just the opposite ... I hardly do *anything* with web forms.
>
>~~Bonnie