Click here to Skip to main content
15,893,594 members

Comments by thams (Top 23 by date)

thams 10-Jan-14 2:17am View    
Yes. as u said its important to handle all exceptions. In my case, this much is enough and I dont want to show any annoying error information to the user. So I'm just showing a nice error window with generic message, and in background capturing all error info into a text file.
thams 10-Jan-14 1:00am View    
Hi,
Thanks for the bunch of tech stuffs.
I've identified my problem. Just made the jit debugger = true in the app config file. This was the culprit. Making it false (or simply delete the line) solved the problem.
Thanks anyway.
thams 10-Dec-13 2:32am View    
Hi, Thanks for reply.
The link shows a workaround, which we are using currently. There is no solution. The real problem with us is, we r not only getting this kind of strange thing with Crystal reports but also with dataset designers. Anyway thanks for your time.
thams 29-Jul-13 8:55am View    
Seems to be no problem with the code. Only left thing is database connection not closed. But definitely thats not the cause of your problem.
thams 14-Jun-13 2:06am View    
Already posted in their forums, but no luck.