This is greate Bonnie BUT,
what if the same column updated from defferant users??, here is the problem.


>Ahmad,
>
>OK, let me elaborate a bit on the "Last Change Wins" thing. First, set things up so that you are accessing your back-end data only through Stored Procedures. In your SP, use parameters for every column in the table. Then, from .NET, you could pass the parameters to the SP only for the columns that have actually changed. In that way, if one user makes a change to one column in a certain row of a table and another user makes a change to a different column in the same row of the same table, they don't wipe out each other's changes because you would only be updating the column where data changed.
>
>Does this help you any?
>
>~~Bonnie
>
>
>
>>Bonnie,
>>
>>No as I said all 3 choices are not the best to let my application work in the correct way.
>>
>>Adding (money) funds to the member records are there. we used the same method #2 before on another application, customers used to come an shout where is the money I paid, last changes win, is not practical for my application.
>>
>>Are these the only choices in .Net?
>>
>>
>>
>>>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