Access Violation on deleting records in CachedUpdates mode
Posted: Tue 30 Oct 2012 03:31
Hello,
I'm using ODAC 8.1.4 with Embarcadero RAD Studio 2010 Version 14.0.3513.24210
I use TOraQuery in CachedUpdates mode. I use TOraUpdateSQL with DeleteSQL, ModifySQL and InsertSQL set.
1)
1.1) When I delete the last record from q:TOraQuery and call ApplyUpdates and get no exception from Oracle, it works fine
1.2) When I get EDatabaseError during call of q.ApplyUpdates, because of my integrity constraints on Oracle, I handle it in q.OnUpdateError and give to user meaningful Warning and write UpdateAction :=uaSkip;
1.3) After showing my dialog box, it raises Access Violation exception.
"Access Violation at address 006149FF ...".
1.4) When I have more than one record in dataset, this exception does not take place.
1.5) I copied Insert,Update,Delete statements into TOraQuery corresponding fields and deleted TOraUpdateSQL. It has no effect. AV Exception remains.
2) The same thing occurs, when I call ApplyUpdates on an empty dataset. But I can prevent it by checking
if q.UpdatesPending then q.ApplyUpdates.
Please help me what to do in first case?
I read in history, that in version
"6.00.0.6 20-Apr-07"
- AV failure with deleting records in CachedUpdates mode fixed
But it still occurs.
I'm using ODAC 8.1.4 with Embarcadero RAD Studio 2010 Version 14.0.3513.24210
I use TOraQuery in CachedUpdates mode. I use TOraUpdateSQL with DeleteSQL, ModifySQL and InsertSQL set.
1)
1.1) When I delete the last record from q:TOraQuery and call ApplyUpdates and get no exception from Oracle, it works fine
1.2) When I get EDatabaseError during call of q.ApplyUpdates, because of my integrity constraints on Oracle, I handle it in q.OnUpdateError and give to user meaningful Warning and write UpdateAction :=uaSkip;
1.3) After showing my dialog box, it raises Access Violation exception.
"Access Violation at address 006149FF ...".
1.4) When I have more than one record in dataset, this exception does not take place.
1.5) I copied Insert,Update,Delete statements into TOraQuery corresponding fields and deleted TOraUpdateSQL. It has no effect. AV Exception remains.
2) The same thing occurs, when I call ApplyUpdates on an empty dataset. But I can prevent it by checking
if q.UpdatesPending then q.ApplyUpdates.
Please help me what to do in first case?
I read in history, that in version
"6.00.0.6 20-Apr-07"
- AV failure with deleting records in CachedUpdates mode fixed
But it still occurs.