>Could you please help me with this?
>
>I have created a client master table with timestamp column named "Updated" , and i retrieved data into a windows form (that inherits from the mmBusinessForm), and then i changed the data in client master table in oracle database(just to test if concurrency work for me)
>
>and then i have made some changes to the same data in the windows form and i am trying to save the entity using the forms save button.
>
>As expected, the entity doesn't get updated (as we have already changed the value of the record in the database manually), but i was expecting it to throw a DBConcurrencyException.
>
>
>but unfortunately it didn't. So will concurrency only work if we update the table by calling the stored procedure directly?
>
>Thanks,
>Vidya

Hi Vidya,

Concurrency should work any time the backend table is changed, not only if you update the table by calling the stored procedure directly. Unfortunately there are currently a number of problems with concurrency when you use timestamps. I do not use Oracle so I am not sure if the problem you are seeing is one of the problems I have reported directly to Kevin, but IF and when he fixes the bugs I have reported, perhaps your problem will go away.

I am hoping for a new release soon, but I have not been given any estimates yet on how soon the bugs will be fixed.

Sam Tenney