Re: dataset safety?

Ausclad,

It is up to you how many times you update the database, be aware that only
changed rows are updated, not a complete dataset. As well can you ask in
advance if a dataset has changes. ds.HasChanges.

The problem lies in the fact if you use an autokey. That is in OleDb
standard not updated by an update in a dataset if that is new. If you use a
Guid as key is this problem gone. AFAIK is this problem gone as well with
SQLClient (I use no auto keys).

I hope this gives an idea,

Cor

"Ausclad" <Ausclad@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:74F87A45-C935-478D-B49B-78983841904F@xxxxxxxxxxxxxxxx
Hi,
I am currently looking at re-writing a payroll/time*** application that
is currently in Access. The users need to enter time*** hours for
numerous
employees.

Up till now I have been experimenting and using strongly typed datasets as
generated by VS. However as these provide a disconnected model, how can I
prevent the loss of user data if the user PC crashes or dies for whatever
reason.

I imagine it would be inefficient to be performing writes to the database
using datasets after every record is inserted.

I like the binding and coding efficiency of using strongly typed datasets,
however it would seem like there can be big overheads and risk in not
updating to the database regularly.

Can anyone recommend a better way?

thanks



.