Hi,

my server has a database table. I read this table on the server into a
dataset and my client retrieves it through a webservice.

No changes on the client and server happen. What's the best way to keep the
data in sync?

I want to avoid that I transfer the entire dataset all the time. Is there
feature of ADO.NET which I can use to find changes and send just them?

Thanks for any hint

Anthony
--
Anthony Malt

Re: Use ADO.NET to keep data between client and server in sync by Cor

Cor
Tue Jan 03 03:20:08 CST 2006

Anthony,

It seems to me that you want to check on the server those rows that are
changed or added later than the last access timestamp and merge those rows
in your datatable time by time.

Is that what you mean?

Cor



Re: Use ADO.NET to keep data between client and server in sync by Anthony

Anthony
Tue Jan 03 04:30:28 CST 2006

Hi Cor,

yes, exactly. In addition I looking for a method to send my client changes
in an elegant manner to the server.

Any thoughts?

Thanks
Anthony

--
Anthony Malt



Re: Use ADO.NET to keep data between client and server in sync by Cor

Cor
Tue Jan 03 05:02:42 CST 2006

Anthony,

My thoughts are as my question. Create datestamps as items in every table on
the (database)server.

Create two kind of services one to get the whole datatable and one where the
timestamp is newer than the previouw retrieval of the data.

And than merge of course the data using the merge in the old datatable.
(What should be easy as long as you give the primary key in the tables or
probably even better in this case add it on the client side).

http://www.vb-tips.com/default.aspx?ID=edb1409d-5394-468f-a63f-de3a5d92b14a

I hope this helps,

Cor