>>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.

I'd say it's two different grids on the same form, possibly in a pageframe. That's what I just did. Page one has a grid. Pages two and three have objects that instantiate their grids in their .UIEnable. They also REQUERY() related views that are .NoDataOnLoad = .T. and set some properties to tell the form which grid was being navigated and possibly edited. If I'm in "edit" mode, each Page.Deactivate will NODEFAULT.

I do all this because all these other tables are related to the same table which deserves to be represented in one consistent form.