A
AnikSol
Development Environment: VB 2005 Prof, SQL Server 2005
In a typical Multi User environment, what is the best way to handle updates
of disconnected datasets of other users.
Eg: User A opens application Winform 1, dataset1 is loaded on his machine
User B opens application Winform 1, dataset1 is loaded on his machine as
well.
Say User A makes changes to Dataset1 and the database has been updated with
the changes. But since User B is either doing something else or may be
editing some records, how to make sure that UserB dataset also gets updated
with the new values from the db.
Any practical / implemented ideas?
Thanks
There have been replies to this post on the windows.databinding forum.
Since SQLDependency cannot be used in SQLServer Express, are there any other
alternatives other than forcing the end client to use SQL Server 2005
Standard Edition?
thanks
In a typical Multi User environment, what is the best way to handle updates
of disconnected datasets of other users.
Eg: User A opens application Winform 1, dataset1 is loaded on his machine
User B opens application Winform 1, dataset1 is loaded on his machine as
well.
Say User A makes changes to Dataset1 and the database has been updated with
the changes. But since User B is either doing something else or may be
editing some records, how to make sure that UserB dataset also gets updated
with the new values from the db.
Any practical / implemented ideas?
Thanks
There have been replies to this post on the windows.databinding forum.
Since SQLDependency cannot be used in SQLServer Express, are there any other
alternatives other than forcing the end client to use SQL Server 2005
Standard Edition?
thanks