HELP! Need Access DB to show realtime changes in different location

[dabooj via AccessMonster.com]

Hi Guys,

I was wondering about how access refreshes it's data within forms and it
seems that it doesn't.
If i have a form open in one location on a network and update fields on the
form the changes are not shown on the form opened in another location.
(I.e. if 2 users are in the same form at the same time and one adds a new
record the other users form will not show this change).

Is there anyway that Access can be setup to show real-time changes over
multiple locations?
Preferably without having to do a manual refresh by clicking a button or
something.

All i want to do is show changes to a form instantly in different locations.

Any help would be greatly appreciated.

Thanks,

Shuja.

 

[Douglas J. Steele]

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)

 

[Keith Wilby]

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 via AccessMonster.com]

I, too, was under the impression that this was exactly the situation that
Refresh was meant to be used for!

 

[Rob Parker]

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

 

[tina]

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

 

[Douglas J. Steele]

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?

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.

 

[Keith Wilby]

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.

Duly noted, thanks Doug.