Dear Rick,
I am referring to data entry and as you said the
requery that I have put in a Timer event does indeed
take the user back to the first entry. How might I
avoid this.
I am working on a database for a transport company of
whom all the users are constantly referring to the one
form open permanently on their screens. Other users
are constantly entering information that needs to be
updated within moments of entry on the screens of other
users, and I'm not quite sure how to do this without the
irritation of returning to the top record?
Do you have any ideas or suggestion?
Thank you kindly
Rhonda
-----Original Message-----
"Rhonda Fischer" <Rhonda.Fischer@Turners-
Distribution.com> wrote in message
Are you talking about design changes to the form or data entry?
In the case of the former, the form is loaded into memory when it is opened and any
changes you would make to the object after it is opened are simply not going to be
seen by other users unless they close and reopen the form. This would only be
possible in Access 97 or older because the newer version don't even allow design
changes unless you're the only one in the file. Even
with the older versions it is a
bad idea.
If you're talking about data entry a form refresh will show changes to existing
records without closing and reopening. To see the
effects of additions or deletions
you would have to issue a form Requery command. The
form's timer event could be set
up to issue either of these commands at regular
intervals, but the Requery would also
cause the form to go back to the first record in the
table. Not something you would
want to do to a user.
If you're talking about a single record form where
everyone is looking at the same