Recent content by SvenHeuer

I have the same since years. It happens very often with the instant client but using the "full featured" client does not help always. I spend a lot of time in this issue but found nothing. It is also on 11 G clients compiled with Delphi XE. Sven

One more request from my side :) I run also in this "brain problem" if I use lobs. Sven

Hi Marco, Thx for this good news.

Hi Marco, is there any schedule for this? Q4 2008 or 2009? Greetings Sven

Hi Marco, the last days I had the "Assertion failed: RowIdAllocations=0" a lot of times. Can you say me, what the DOA is checking here and what is wrong?

I think, he would like to embed the oracle monitor into an own application. (Yes, would be nice :) ) Greetings Sven

Any news (timeframe) to this topic? Greetings Sven

Ok, i added a new procedure procedure TOracleDataset.CancelRecordUpdate; Var Log : TChangeLogItem; BM : TBookmark; begin inherited; if State in [dsEdit, dsInsert] then Cancel; bm := GetBookmark; Log := FindChangeLogByBookmark(PInteger(bm)^) as TChangeLogItem...

Hi Marco, is it possible to cancel the change of only one record (after i scrolled to another record)? Something like this: DataSet.Cancel; bm := DataSet.GetBookmark; Log := DataSet.FindChangeLogByBookmark(PInteger(bm)^) as TChangeLogItem; DataSet.FreeBookmark(bm); Log.Cancel; I can't do...

No, this problem is solved. (at least on my system) If i have Lockimmediate and roRefreshBeforeEdit=false i also get an "Record has been changed" error. (and cachedUpdate=true) Setting roRefreshBeforeEdit=true and the error is gone Greetings Sven

Marco, may be this is the same problem as i described? Seeting refresh-option roBeforeEdit to true solved this problem. Is LockImmediate also on true? I suppose there is a problem with LockImmediate. Greetings Sven

Marco, I found out, that in my mdi-application i had an "abort" in a OnCloseQuery event. Due this, the datamodule forms didn't close the datasets and the datamodules aren't freed. So doa tries to close all the dataset and throws the AV's. After removing the abort-command it's better, but still...

Marco, i have some AV when shutting down the application. After LogOff The TOacledataSet.DataEvent is called and an av occured on inherited;. later... raise Exception.Create('Assertion failed: RowIdAllocations = 0'); Greetings Sven

Great Job, our application (>600k lines of code) is still running without any problems ;-) . (ok, there are problems, but not due doa 8-) Update took 5 minutes. Guys: Your'e are great. Greetings Sven

Both versions