Devart Forums

Hello,

Delphi 7, ODAC latest release, Win 7 x64.
TOraSession, TProvider, TOraTable on the server side and a TClientDataset on the client side.
The TProvider has set the UpdateMode property to "WhereKeyOnly".
The table definition is below.

• create table BRANCH (
  BRAID NUMBER(9) not null,
  BRACODE VARCHAR2(25),
  constraint PK_BRANCH primary key (BRAID)
  );
  
  create sequence BRANCH_seq nocache;
  
  CREATE OR REPLACE TRIGGER BRANCH_BeforeInsRow BEFORE INSERT ON BRANCH FOR EACH ROW
  begin
  select BRANCH_seq.nextval into :new.BRAID from dual;
  end;

After successfully insert one record, trying to update the BRACODE field generate the error from the title.

If I set the table's KeyFields property to "BRAID", I can update the record without incidents.
Same, if the TProvider's UpdateMode property is set to "WhereChanged", or "WhereAll".

But having 200+ tables object in the server side, this is out of question.
Same application works perfectly with SDAC.

Although the error was reported on the SDAC forum under the same title and the moderator said that it was fixed, in ODAC at least, it is not.

I hope in a quick solution.

Thank you,
Radu B.

We have reproduced the problem - and we will investigate the reasons for such behavior.

Hello,

Any news?
A workaround, bugfix, anything?

I cannot update the application.....

Thank you,
Radu B.

We do not yet fixed the problem. As soon as the problem is fixed we send you the updated version of the product.

Much appreciated.

I have an urgent request from one of my Oracle clients and I cannot deploy the middle tier server.
Do you have any bugfixed kit?
Is it possible to get it until monday?

Thank you,
Radu B.

What's going on with this issue?
No info for almost 2 weeks...

Hello,

With whom should I ask to solve this PROBLEM???
I was amended from my clients because the application isn't working!

It has passed almost o month from your confirmation and more then 2 since when I raised the problem.
The situation is totally unacceptable.
I am thinking finding another provider for this engine!

We have investigated this behavior. Unfortunately, this problem is due to the TDataSetProvider behavior, and we can't influence it.

I disagree with the final response, because in ODAC version 6.90, this behavior doesn't appear, so you could at least, somehow put the this functionality back.

...no reaction..

I have a miserable life, uninstalling DACs, installing ODAC v6.90, compiling the application, deploying it, uninstalling ODAC, installing the last version of DACs and if something goes wrong, starting the whole process.

Just isn't any way to solve it?

One of your commitment is "high-quality user support", but appears to be just simple words, at least in this case.

You'll get ignored, just like my issue http://forums.devart.com/viewtopic.php? ... 88#p100885 has been. Anything awkward for them to investigate or fix (often broken by a change they've made) will get ignored by their support, even though they say in their company information :

"High-quality user support - we stick to our strict support policy and put great effort to help them solve problems in no time"

Yeah, right....

Wonderful!!!

Devart release a new version with the same old bugs introduced by they!
Thanks a lot DEVART!

Have a nice working day!!!!

Hello!

YOU have bugs in the ODAC product! More, introduced by YOU, since in the older version aren't.
When will you correct them?

In both ODAC versions (6.90.0.60 and 9.3., on an attempt to update a record, the same error occurs: 'Record not found or changed by another user' . As I wrote you earlier, this problem is due to behavior of TDataProvider. If you work directly with OraQuery, such problems won't occur. If you are able to create a small test sample, in which the problem wouldn't occur on old ODAC versions, please send it to us - and we will try to reproduce the problem once again.