strange concurrency problem

  • Thread starter Thread starter Bernie Yaeger
  • Start date Start date
B

Bernie Yaeger

I'm running into a strange concurrency problem:

I have an outer loop of distinct invnum from table a_r; I have an inner loop
of table a_r2 that is filtered on 'invnum = out loop invnum'. I calculate
and then want to delete, but I have the concurrency error, which I supposed
was because the out table is from the same backend table. So I came up with
a strategy - I created a table called a_rtemp before creating the outer
loop. Now my outer loop refers to a completely different table, a_rtemp -
yet I am still getting the concurrency errror! Any idea what's going on
here?

Thanks for any help.

Bernie Yaeger
 
The concurrency problem exhibits during the delete? What are the symptoms? (delete fails, seek fails, ...?

What are the foriegn key restrictions?
 
Hi Dave,

It's very strange: I loop through the dataset and make changes, update the
changes, end by calling acceptchanges. Then, when I try to loop through it
again, the changes are rejected on this concurrency issue. If I open a
completely different datatable after the first loop and changes, it will now
allow this second loop of changes, no concurrency issues.

So I have the workaround, but it's bizarre behavior - almost as if using
acceptchanges locks it away as no longer changeable, if that indeed is what
triggers this - I'll test.

Thanks,

Bernie

Dave said:
The concurrency problem exhibits during the delete? What are the symptoms?
Click to expand...
(delete fails, seek fails, ...?)
 
I have an app that manipulates a 30+ table database with some fairly intricate business rules. I've had to use work arounds several times. So, that you need to use a work around does not surprise me. Glad you found a way to make this part of your app work.
 
Back
Top