That makes a lot of sense to me.

Would you have a property in your button set class to hold the view/table alias that your actions can use to be sure they act on the correct table alias?

What preference to you have on using views vs tables on a maintenance type form (low user count environment)?


>That would certainly work. It might be more intuitive to have 2 add/delete/revert buttons sets, one always dedicated to he top grid, and one always dedicated to the bottom. Either way is doable, just depends on user preference. Sounds like your getting close to a working solution...

Thanks