You could have an "Update View" button that the user clicks when they're ready. The timer idea is pretty good, but what if they get a call while they're spinning and pause to answer. Then you update but they're neither where they'd last wanted to be nor where they're trying to go? Also, you could enable/disable the update view button so it's (relatively) obvious that they need to click it. Like a GO button on web search pages...

I agree that the interactive method probably isn't a good solution in this case.

>I have a simple form with a spinner where a user can change the year to display data in a grid for. The grid has a parameterized view (LogFile.Year = ?lnYear) where lnYear is derived from the value of the spinner. When the user spins the spinner, at what point would you Requery() the view to refresh the data in the grid?
>