>>Your way is workable too, but if you use heavy customization, e.g. custom grid.controls with some subclassed code in events, then you may be forced to use Add/Remove objects any time you refill recordsource. Not a big deal again, but will take comparable or more amount of coding.
>
>I guess another method is to use views as the source. I don't do this much, but with views you should be able to perform "catastrophic" table changes without concern about the grid objects, as long as the view base fields aren't structurally altered, just relying on Requery() for updates...

Hmm... I thought the same, but it was reported here few times that view's requery can also yield blank grid (or lose customization, at least) in some situations. I did not see it myself, because I don't use them much too.