S
snooka9
I'm testing the use of an Access XP front-end (FE) with an SQL 2005 back-end
(BE) and I've encountered a minor issue which didn't occur when it was an
Access FE / BE.
I have a form bound to a query with multiple "joined" tables, all of which
are linked tables from the SQL BE. I noticed that if I have the form open on
multiple workstations then edit and save a record from one of them, the other
workstations do not reflect these changes, even if I move to a different
record and back. BUT, if I try to edit the same record on any other
workstation afterwards, I get the message "The data has been changed.
Another user.....Re-edit the record." and it then refreshes the record and
the initial changes I made appear.
I could put a "Me.Refresh" in the Form_Current event BUT I read somewhere
that this can be costly overhead because it creates excess network traffic.
In my case, this particular form's records won't be edited too often....maybe
a few times a day, but its important that these changes are reflected to
everyone's workstation.
Is there any other way to handle this other than using the Me.Refresh
command? Am I missing some option that needs to be used now that the data is
from an SQL BE instead of an Access BE?
Thanks in advance.
snooka9
(BE) and I've encountered a minor issue which didn't occur when it was an
Access FE / BE.
I have a form bound to a query with multiple "joined" tables, all of which
are linked tables from the SQL BE. I noticed that if I have the form open on
multiple workstations then edit and save a record from one of them, the other
workstations do not reflect these changes, even if I move to a different
record and back. BUT, if I try to edit the same record on any other
workstation afterwards, I get the message "The data has been changed.
Another user.....Re-edit the record." and it then refreshes the record and
the initial changes I made appear.
I could put a "Me.Refresh" in the Form_Current event BUT I read somewhere
that this can be costly overhead because it creates excess network traffic.
In my case, this particular form's records won't be edited too often....maybe
a few times a day, but its important that these changes are reflected to
everyone's workstation.
Is there any other way to handle this other than using the Me.Refresh
command? Am I missing some option that needs to be used now that the data is
from an SQL BE instead of an Access BE?
Thanks in advance.
snooka9