We used many TSmartQueries whose SmartRefresh were set to true in the data module of the project to connect dictionary tables one by one, which is the most frequently-used method of development. However, unfortunately, it was the turn that we developed modules of report, where we also used some TOraQueries or TSmartQueries to select data, a problem came out. A few minutes after the PREVIEW button was pushed down, the data was selected out and the Excel report was made out, but there were two oracle exceptions following it, their error code are 1036 and 24337, which can not be catched in the OnException event of the main TOraSession, even though TApplicationEvents are resorted to. If we closed the SmartRefresh Property(set it to false), this problem would be solved.
Should I discard the benifit from SmartRefresh? How can I catch the two exceptions?
SmartRefresh conflicts with most-costed SQL Query, raises exception which can not be catched easily and usually
-
Peng
Is there anyone who can help me? Is Alex in?
HELP!HELP!HELP!!!!
Perhaps Most-costed SQL query can guide people to make a mistake, what I really want to mean is that a lot of things are done in the loop from
the first record to the last one in dataset and the cycle carries heavy burden and costs a lot of time.
HELP!HELP!HELP!!!!
Perhaps Most-costed SQL query can guide people to make a mistake, what I really want to mean is that a lot of things are done in the loop from
the first record to the last one in dataset and the cycle carries heavy burden and costs a lot of time.
SmartRefresh option uses TOraAlerter component internally, which uses its own TOraSession object and runs in its own thread. You can't get access to this OraAlert object to handle its OnError event. But you can use
TOraErrorHandler or global application OnException event handler to intercept these exceptions.
TOraErrorHandler or global application OnException event handler to intercept these exceptions.
-
Peng
Could Alex can look at this again, I still need your help.
Alex, a new accident happens. It seems that we can catch the two exceptions only at ODAC of version 5.55.0.20, but have no way to deal with this problem at newer versions or older ones. We don't know why this problem can stand. Alex, we still need your help.