>It sounds like you should really be using views. Someday, I'll get around to them myself. But for now, zapping the Grids.RecordSource property works for >me. We built code into our base grid that saves/restores the column stuff. And now with Access/Assign, it's all "behind-the-scenes".
>
>Yes, like views myself and maybe more appropriate, but I think there is one downer with views. When the structure of an involved table(s) change, you must virtually recreat the views, and if it's a complex view it can be disheartening.

I know what you mean, that's why we didn't use views in the first place! When we go to views, we'll probably use programmatically created ones in a temporary DBC so they'll always match the current structure.