>Interesting point. I generally assume that any form that is expected to return or set a value probably "should" be modal, because if it is not, you gotta do a lot of hand-waving and peeking and poking to see what has been happening in the "secondary" form. In that case, I suppose one might as well turn on some actual event handling for a cleaner process.

If you want a modeless form to return a value, then the passing of an object with properties to hold the values works very well. But the object has to exist globally at the calling program to the modeless form. In this case setup an event and bind a UDF to it. Then in the modeless form, raise the event when returning. You also need to take care to remove the modeless form if the calling form/procedure ends (nothing to return to...).