>>While it may be easier to implement at first, having two different forms could lead to future maintainability problems. With one form, bugs and enhancements can be done in one place.
>
>Yeah, if any code needs to be the same, you can write a class for the resuable code. But if you need a to pass a parameter to the load event, to tell it what tables to open and how to build the grid, doesn't it sound like its two different forms? I dunno, it just seems obvioius to me.
>
>>P.S. You haven't been on vacation this whole time, have you? :-)
>
>Kindof, vacation from the UT. :-) Actually, I have today off, so I'm gonna catch up pn 10,000 messages.

Mike, just don't post 10,000 answers please, or we all will need a vacation... :)