<<
One question... What if the user re-orders the columns at run-time?
<<

True. If the user wanted to do this (via dragging and dropping the columns), when it came time to swap the under-lying recordsource, I would make sure the grid was first put back to its default positon, and then if need be, programmatically re-arrange the columns via the columnorder property.

I think the issue rests on ensuring the grid is placed back into a position that is compatible with the underlying cursor. When one uses RV's, perhaps from a DataEnvironment, the control sources of the columns get set. This creates an issue. However, it is not an insurmountable one. My basic point is that extra work is created. In the end, regardless of whether you use RV's or SPT, swapping things around is feasible. Depending on how you implement things, it may entail more work..

Glad you jumped in. It is an excellent point to bring up...

Thanks :),