Cetin,

[With a show(1) you wouldn't need read/clear events. Hide() the form to continue on the line that follows read events. You'd get the value and release the for there.]

That works. Thanks.


[PS: I didn't understand why "but if the dialog required more complexity, a class would be better" other than preference.]

In this class, I've got only one "parameter" (property). Other dialogs could have several properties which could be mutually exclusive. Rather than have to pass in parameters in a specific order, I'd rather set properties in which ever order I choose. Basic OOP design philosophy.

Regards,
Thom C.