> Hello. I've set this setting before, I think - or else I coded it that
> way.
[quoted text clipped - 8 lines]
> too.
> Thanks in advance.
Requerying the form automatically takes the user back to the first record.
Even if you write code to bookmark the current record before the requery and
return to that record, requerying every 30 seconds isn't going allow time to
do much else with the database, including entering when a new appointment
arrrives. It would make more sense, to me, to either place a comand button on
the form so the user can requery before they check on arrivals, or better yet,
requery each time after an new arrival is entered.

Signature
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Ken Snell (MVP) - 05 May 2007 18:53 GMT
Yes, requerying will cause user to go back to first record. That may or may
not be a problem with the form, depending upon its design and purpose.
For example, a form that is "read only", and that is filtered to show
records in reverse chronological order, and that are at most x minutes old
(older records are not shown) would be a fine form for using a timer event
and a requery action.

Signature
Ken Snell
<MS ACCESS MVP>
> Requerying the form automatically takes the user back to the first record.
> Even if you write code to bookmark the current record before the requery
[quoted text clipped - 7 lines]
> yet,
> requery each time after an new arrival is entered.
missinglinq - 05 May 2007 20:28 GMT
And, of course, having the receptionist pick up the phone and saying "Mr.
SoandSo is here for his appointment" would probably take less time and be
more effecient!

Signature
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000