Ahmad,

We use #2, last changes win. But, it depends on your application as to whether that's the best way to handle things or not, in our case it is. Typically, record locks are not a good solution. Have you read Kevin's book yet? I haven't finished reading it, but I'm betting that he probably has a discussion about this topic in his book. I don't have it with me right now, otherwise I could look it up and quote a few things for you. Our solution works for us, but it may not be right for you.

~~Bonnie



>Hi Bonnie,
>Well, this is not what I read in the books!!!!, anyhow I take you word as garanty:)
>
>One thing confusing me, one of the tips in these .Net books says about resolving data conflect that, the rool will be :
>1. First changes wins
>2. Last changes wins (OR)
>3. List the conflicts and can let the user to deside which update to take effect.
>
>From the experiance, NO WAY to let the user deside that, and also I don't like the other 2 points 1 & 2, in network environment this code me a mess.
>
>For me in the previous languages I used to develop, most of the time I used RecordLock with many handels to the other users when they open the same record. now in .NET I am still new to .Net and trying to get the correct technique.
>
>So, What do you suggest?
>
>
>>Ahmad,
>>
>>In .NET, there is basically no such thing as a Connected DataSet. You are always using disconnected DataSets.
>>
>>~~Bonnie
>>
>>
>>
>>>Hi All,
>>>
>>>I know that if Disconnected dataset mode used in the application, there is a proble, that you need to dicover and resolve data conflicts!!.
>>>
>>>So, Which one is better to use Connected or Disconnected dataset mode?
>>>
>>>Thanks in advance