>Edward,
>Thanks for the quick response. What you have suggested does work but it completly replaces the grid with the controlsource table. I then loose the grid column headers that were originally set up for that particular grid. Any other suggestions? Thanks again.
>John Symons

John, it's not my suggestion kills the headers, it's the way you handle the grid , just remember that initially you had completely blank grid, so some progress is here :).
There are two ways to work with somewhat dynamic grid, i.e. grid which changes it contents (recordsource) according interface/application flow. The first way is that you track all these changes by restoring grid settings. Usually, it includes grid.recordsource and column.controlsources but may also include column.columnorder, column.width or even header.caption; though extensive number of settings may indicate some design flaws. Another way is to base grid permanently on read-write cursor. When you want to show something new grid, it will mean deleting/inserting new records to this cursor, but link between the cursor and grid will not be broken, and grid settings will stay unchanged.