>>>>>>>Secondly I don't use SQL through; my application is using CA. And I do use SQLExec(). But the SQL Select/Insert/Update do not give me any problems since I learned how to catch them right at the point where they are executed. When I look at some customers' error log I see mostly the error caused by a problem instantiating objects. And so far, I have not learned how to catch those.
>>>>>>
>>>>>>CA is also SQL :). I use prg-based CA class and in each of the after* methods there's a check for the lResult parameter, and if .f., aError(ea), then olog.logArray(@ea).
>>>>>>
>>>>>>Just now I got the idea that I could pass this as a parameter - logging the state of the cursor adapter may also help.
>>>>>
>>>>>Maybe I should simply not have any bugs in my application and therefore won't need to log errors :)
>>>>
>>>>
>>>>too much effort to implement now. Inform your users that it is a feature...
>>>
>>>After tonight this will be a moot point, as I intend to win the big lottery. The winner gets about $700 million tonight.
>>
>>Understood. After that win I will charge 1$ for every line I write to you...
>
>Sounds very fair price. I didn't win and happy about it. Life would be too complicated. This morning I received texts and photos from my younger daughter hiking with a bunch of other young people through towns of Norway. This is much happier news than having to deal with millions of dollars.

Sorry for jumping in, but I noticed the word Norway. Do you happen to know which towns your daughter visited?