Concurrency problem

Thread is closed for posting
4 posts, 0 answers
  1. oVan
    oVan avatar
    35 posts
    Member since:
    Apr 2008

    Posted 10 Nov 2009 Link to this post

    I created a simple type Agency, forward-mapped it to ansql-database, then in my web application I added an OpenAccess datasource and aRadListView. I can add new records, but when I edit a record and then save it, Iget “Concurent data changing operation detected”.


    So, I found this help page:

    I don’t understand that I need to implement such amount ofcode just to perform a simple insert or delete?


    In addition, I also found this KB-topic:


    I thought the whole point of an ORM was to simplify things,not complicate.


    Am I missing something here?


    ps: note also the typo in the original error message. It should be "Concurrent".

  2. Zoran
    Zoran avatar
    534 posts

    Posted 11 Nov 2009 Link to this post

    Hello oVan,

    Using the OpenAccessDataSource does not require any concurrency logic explicitly implemented by the user. Nevertheless, we were unable to reproduce your exception with the information you provided in your previous post. Could you send us the simple class that you have tested with so we can see if there are some special cases that we do not handle properly.

    All the best,
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
  3. oVan
    oVan avatar
    35 posts
    Member since:
    Apr 2008

    Posted 12 Nov 2009 Link to this post

    Hello Zoran,

    That's what I thought (and expected) also. I'll try to make a small project later today to demonstrate this.

  4. Madrinha
    Madrinha avatar
    12 posts
    Member since:
    Sep 2012

    Posted 28 Nov 2009 Link to this post


    I had the same problem when using OpenAccess ORm on a radgrid. After all the problem was that with the copy/ paste from another webform I've forget to change the ID to the new ObjectID. All I've done was:
      <MasterTableView  DataKeyNames="NewID"

    I'm using the template.master ObjectProvider approach.

    Hope this helps.

    Eduardo Barbosa

Back to Top