Strange TOraQuery behaviour

[brekhof]

Delphi 7 Pro SP1, ODAC 5.55.0.19, SDAC 3.55.0.15

I'm running a conversion program from Pervasive to either Oracle or MSSQL. Everything works fine except for one thing:

All errors get logged to a memo component (memo2) which is also written to disk with memo2.lines.savetofile(). After copying records to Oracle and creating the indexes for a table using a TOraQuery then if a duplicate index error occurs then (and only then) the TOraQuery in question raises an error, the try except catches it but the memo does not get updated on screen but after saving the same memo to disk it only contains the errormessage that is not shown on screen?? The strange thing is the fact that we are talking about the same memo-component. When copying/ndexing the same data with the same logic to MSSQL everything works as expected (the memo on screen matches the log on disk).

Switching back to 5.50.0.18 does not change the error.

regards,
Martin

[brekhof]

I noticed that using 1 OraSession component and a OraTable and a OraQuery component will open two (2) session with the Oracle (9i) server. Is this to be expected?

regards,
Martin

[Alex]

We need more detailed description of your memo problem, and if it is possible send us small demo project that demonstrates your problem and script to create server objects. Please, send a message to our ODAC support e-mail address.
As to your second question(two opened sessions on Oracle) it is possible if you set TOraTable.SmartRefresh property to True, in other case check that the second session is not an IDE design-time opened session (just set TOraSession.Connected property to False in the form editor).

[Guest]

send us small demo project

Creating the small project I found out that I was in error, case closed.

regards,
Martin