Thanks. I was thinking that I would need to requery(). The Activate() of the form is a good idea, and should be plenty often enough.


>You would Requery( ) the view to update it from the underlying table. One idea is to put this code in the Activate( ) method of the form. That way if a person is using a form that displays the list, and flips over to another form to update the table which feeds the list, then the display in the original form is updated automatically when that form is re-activated.
>
>As for detecting updates made by other users, I suppose you could use a timer to do a requery every so often, but that doesn't sound like good design. If the underlying table isn't being updated all that often, I wouldn't worry about doing automatic updates in an open form.
>
>>I've created a view for my reports, and so my user can look at records with all the "words" for categories instead of codes.
>>
>>If someone were to change a value in the underlying data, how would I be sure the change shows up in the view if it's open? Somehow I thought it was connected to SET REFRESH, and if I waited a few seconds the changes would show up.
>>
>>Are the contents of the view set in stone each time I open it, as if it were an SQL SELECT?
>>
>>The data won't be changing all that much once the view is open.