J
James Cadd
Please forgive the restatement of my post from a few days
ago, but I hope this question is more clear. I'm working
with a C# Windows Forms app.
What is the best practice for handling the changes made
by a user that occur after an asynchronous update has
been initiated, but before the update has completed? The
TaskVision sample application simply discards any data
returned by the data access web service if the user has
made any updates while the asynchronous update was
running. I'd like to merge this data back into the
client application, even if the user has made changes.
Which is a better way to do things?
Thanks in advance.
ago, but I hope this question is more clear. I'm working
with a C# Windows Forms app.
What is the best practice for handling the changes made
by a user that occur after an asynchronous update has
been initiated, but before the update has completed? The
TaskVision sample application simply discards any data
returned by the data access web service if the user has
made any updates while the asynchronous update was
running. I'd like to merge this data back into the
client application, even if the user has made changes.
Which is a better way to do things?
Thanks in advance.