title: How to solve Optimistic Concurrency Updates in c# .NET N-tier applications?
body: <p>Hy everyone.</p>
  
  <p>In c# .net VS 2008 I'm developing an N-tier CRM framework solution and when it's done I want to share it. </p>
  
  <p>The architecture is based on:</p>
  
  <p>Data Access Layer, Entity Framework, Bussines Logic Layer, WCF and finally the presentation layer (win forms).</p>
  
  <p>Somewhere I had read, that more than 2 tier layers are problematic, beacuse of the Optimistic Concurrency Updates (multiple client transactions with the same data). </p>
  
  <p>In max. 2-tier layer solutions this should not be a problem because of the controls (like datagridview) that are solving this problem by themself, so I'm asking myself if it's not better to work with 2-tier layers and so avoid the optimistic concurrency problem?</p>
  
  <p>Actually I want to make an N-tier layer solution for huge projects and not 2-tiers. I don't know how to solve concurrency problems like this and hope to get help right here. </p>
  
  <p>Certainly there should be good some mechanisms to solve this... maybe any suggestions, examples, etc.?</p>
  
  <p>Thanking you in anticipation.</p>
  
  <p>Best regards,
  Jooj</p>