Echo? Paint? Repaint? multi-user db forms keep refreshing

[Bobbi]

I am wondering if any of the following properties will help with my problem:
Paint, Repaint, Echo, Requery. Comments, please!

I developed a database that is used to track road conditions during weather
events. The data input form starts with a lookup to the streets table, then
they tab to the subform to record info such as caller name, specific
problem, etc. My problem is that Access refreshes the info, so one user
might be inputting info for Main Street and in 1-60 seconds, another user's
lookup field will change to the Main Street record. I don't want this to
happen.

I just split the database and copied the front end to the C drives, thinking
that if they weren't looking at the same form, that would fix it. It didn't.
Is changing the refresh rate the only way around this? Are there any known
performance issues with changing that rate? Any insight would be
appreciated.

Bobbi

 

[Dirk Goldgar]

I am wondering if any of the following properties will help with my
problem: Paint, Repaint, Echo, Requery. Comments, please!

Answered in the .forms newsgroup, where you posted this question
independently. That's called "multiposting", and it's generally frowned
on because others don't know what answers have already been given, and
so they duplicate the effort. Also it's harder for you to keep track of
the various replies, and it's harder for later readers of the question,
who may be looking for the same answer, to learn what they need.

In most cases a single, well-chosen newsgroup will do. If your question
really is relevant to more than one newsgroup, the approved technique is
to "crosspost" it instead, by listing multiple newsgroups in the To: or
Newsgroups: line of a single message. If you do that, the message and
any replies will appear in all the listed newsgroups automatically,
which is beneficial to all concerned.