
Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> You can set the form's TimerInterval property to an appropriate time (its
> value can be between 0 and 65,535 milliseconds), and put code in the forms
> Timer event to do a requery (using Me.Requery)
Hi Doug,
Wouldn't that have the unwanted side-effect of setting the current record as
the first in the set? Would Refresh be a better alternative?
Regards,
Keith.
missinglinq - 23 Mar 2007 13:59 GMT
I, too, was under the impression that this was exactly the situation that
Refresh was meant to be used for!

Signature
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Rob Parker - 23 Mar 2007 14:17 GMT
Interesting thread ...
My understanding is that Refresh will cause changes to the current
form/record to be displayed (eg. it will refresh calculated controls),
whereas Requery will update any changes to the form's recordsource (and,
quite likely, change the record being displayed on the form); the Requery
will also trigger a refresh for calculated controls. I await further
clarification from the experts.
Rob
> I, too, was under the impression that this was exactly the situation that
> Refresh was meant to be used for!
tina - 23 Mar 2007 14:49 GMT
from Access 2003 Visual Basic Help:
"The Refresh method shows only changes made to records in the current set.
Since the Refresh method doesn't actually requery the database, the current
set won't include records that have been added or exclude records that have
been deleted since the database was last requeried. Nor will it exclude
records that no longer satisfy the criteria of the query or filter. To
requery the database, use the Requery method. When the record source for a
form is requeried, the current set of records will accurately reflect all
data in the record source."
hth
> Interesting thread ...
>
[quoted text clipped - 9 lines]
> > I, too, was under the impression that this was exactly the situation that
> > Refresh was meant to be used for!
Douglas J. Steele - 23 Mar 2007 15:33 GMT
>> You can set the form's TimerInterval property to an appropriate time (its
>> value can be between 0 and 65,535 milliseconds), and put code in the
[quoted text clipped - 4 lines]
> Wouldn't that have the unwanted side-effect of setting the current record
> as the first in the set? Would Refresh be a better alternative?
A lot depends on what the users want, but I think a Requery is what's
required. You can always bookmark the current row, do the requery, then
reset the current row based on the bookmark.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
Keith Wilby - 26 Mar 2007 09:33 GMT
>> Hi Doug,
>>
[quoted text clipped - 4 lines]
> required. You can always bookmark the current row, do the requery, then
> reset the current row based on the bookmark.
Duly noted, thanks Doug.