Very good point, Larry, thanks, and I am already firing off a modal screen to edit the contract clauses in an OLEBound field. Unfortunately, the edit-on-request architecture makes the whole requery, update, revert shtick difficult with grandchild tables. The current architecture was the easy way out when I designed the app.

>However, if you can spread that information over several UI interfaces (e.g. pages on pageframes) and requery the appropriate views when needed (like delayed instantiation), it will probably help performance all the way around.