Re: tricky TimeSpan editing

thank you for the information. It was very informative.

If i do implement transactions, then I will probably employ it at the
t-sql level, instead of bloating my code more. Whenever I can do
something on the backend in t-sql, I try to do it there to save
bandwidth and processor usage.

I'm thinking that I might be able to port some of the original code
over to t-sql. For instance, the part of the code that fixes all of the
endtimes at the very least. But since most parts of this do need to be
processed in code, I might have to adopt ado.net transactions as well.

In reality, there will be only one user editing their time*** at a
time. The "admins" (about 3 of us) will be editing other peoples
timesheets but not even at this level, only if there is a problem or
they can't figure something out (more of a support standpoint)

Thank you sir for all your information, you have been extremely helpful.

.