Devart Forums

Hello,

I use Delphi 7 with ODAC 5.80.0.41 Net and Oracle 10.2.0.3.

I encounter a problem with local sorting of a Timestamp column.

An access violation exception is thrown after one or sometimes several clicks on the column header.
It seems that specific data (timestamp values) is required in order to cause the bug to appear – we have the same table (structure – not data) with the timestamp column on different schemas and the exception appears only on one out of four schemas. When I copied the rows where the bug definitely appears from our production schema to a test table on our development schema, the bug is constantly reproducible.

I sent a test project where the bug can be reproduced, the table script and the exception log produced by EurecaLog to [email protected].

Here are steps to reproduce:
- Change the OraSession settings;
- Run the project;
- Sort by ID;
- Several times sort by TX_TIMESTAMP; //sometimes the bug appears after the first sorting on the Timestamp column.

Note I compiled the project with runtime packages as I do in my application. I copied the packages we use as is, though for this project, I believe, dac70.bpl and odac70.bpl are enough.

We are short time before an important production to one of our customers and the report where the bug occurs is one of our core reports, so please assist with this problem as soon as you can.

Thanks,
Yevgeny

We have fixed this problem. The fix will be included in the next build of ODAC.