Linked table doesn't update

  • Thread starter Thread starter Steve F via AccessMonster.com
  • Start date Start date
S

Steve F via AccessMonster.com

I have a back end db (Access 97) that is updated with data once a minute.

A front end (Access 2002) db links to a table in the back end and a form
displays the data to the user. On my workstation (XP-pro), this form updates
as the back end data changes.
I've copied the front end to the clients office workstation (Access 2002/XP-
pro) and it works fine, providing a continuously updated display of the data.
However when I copied the front end to the clients production workstation
(Access 2002/NT4), the form no longer continuously updates. On opening the
form, the latest data is displayed but the linked table then stops updating
when the back end changes until the form is closed.
This is somewhat frustrating as the purpose of the database is to provide the
production people with a continuously updated display of data.

Has anyone experienced this sort of behaviour?

The only apparent difference between the clients office and production
workstations is the operating system. Access 2002 was installed on the NT4
workstation together with all the required system files so I would have
expected it to behave exactly the same as on XP-pro. Has anyone had problems
with using Access 2002 on NT4?

Any help appreciated.
 
Steve said:
I have a back end db (Access 97) that is updated with data once a
minute.

A front end (Access 2002) db links to a table in the back end and a
form displays the data to the user. On my workstation (XP-pro), this
form updates as the back end data changes.
I've copied the front end to the clients office workstation (Access
2002/XP- pro) and it works fine, providing a continuously updated
display of the data. However when I copied the front end to the
clients production workstation (Access 2002/NT4), the form no longer
continuously updates. On opening the form, the latest data is
displayed but the linked table then stops updating when the back end
changes until the form is closed.
This is somewhat frustrating as the purpose of the database is to
provide the production people with a continuously updated display of
data.

Has anyone experienced this sort of behaviour?

The only apparent difference between the clients office and production
workstations is the operating system. Access 2002 was installed on
the NT4 workstation together with all the required system files so I
would have expected it to behave exactly the same as on XP-pro. Has
anyone had problems with using Access 2002 on NT4?

Any help appreciated.
Click to expand...

What code are you running to make the updates appear? I ask because the machine
you have the problem with is the one exhibiting normal behaviour for Access. An
opened form will only show the data that existed at the moment it was opened
unless *something* tells it to take a fresh look. If you do not have code or a
macro forcing a requery on the form in the Timer event then you shouldn't be
seeing automatic updates on any of the machines.
 
Rick said:
What code are you running to make the updates appear?
Click to expand...

Sorry - should have mentioned in my original post that the forms Timer
Interval is set to 60000 and the On Timer event refreshes the form using Me.
Requery. This works as expected on the XP workstations - the form refreshes
every minute and displays the latest data from the backend.

On the NT4 workstation, Me.Requery sees no change to the data because the
linked table is not updating with the changes to the backend.

It's as if opening the form is locking the table, preventing any updates
until the form is closed.
 
Steve said:
Sorry - should have mentioned in my original post that the forms Timer
Interval is set to 60000 and the On Timer event refreshes the form
using Me. Requery. This works as expected on the XP workstations -
the form refreshes every minute and displays the latest data from the
backend.

On the NT4 workstation, Me.Requery sees no change to the data because
the linked table is not updating with the changes to the backend.

It's as if opening the form is locking the table, preventing any
updates until the form is closed.
Click to expand...

"Thie linked table is not updating"? What's in the front end (the link) is
a pointer. If others are modifying the table that the link points to then
it IS getting updated. Are you saying that while this user has the form
open *nobody* can do updates or only that they can't be seen by this user?
 
Rick Brandt wrote:
[clip]
"Thie linked table is not updating"? What's in the front end (the link) is
a pointer. If others are modifying the table that the link points to then
it IS getting updated. Are you saying that while this user has the form
open *nobody* can do updates or only that they can't be seen by this user?
Click to expand...

The table in the backend database is getting updated.
It is only this user that cannot see these changes whilst the form is open.
 
Steve said:
Rick Brandt wrote:
[clip]
"Thie linked table is not updating"? What's in the front end (the
link) is a pointer. If others are modifying the table that the link
points to then it IS getting updated. Are you saying that while
this user has the form open *nobody* can do updates or only that
they can't be seen by this user?
Click to expand...

The table in the backend database is getting updated.
It is only this user that cannot see these changes whilst the form is
open.
Click to expand...

Well I'm stumped then. In my experience Me.Requery is exactly the same as
closing and opening the form in this respect.
Are you positive the Timer event is even firing?
 
Rick said:
Well I'm stumped then. In my experience Me.Requery is exactly the same as
closing and opening the form in this respect.
Are you positive the Timer event is even firing?
Click to expand...
The timer event is definitely firing - I added an extra unbound field to the
form and added a line of code to the On Timer event to write the current time
to this field. This field updates whilst all those bound to the linked table
do not.

I also tried replacing the Me.Requery event with code to close the form and
then re-open it - again the data does not update!
 
Back
Top