Victor,

I like the idea of capturing screen schots automatically. We may implement it in our Error Handler routine.

BTW, there was a quite interesting situation today. The Error Handler tried to report an error and it failed, because our Error Log table has two unique fields and the NewID() SP could not find some constant. The errors were nasty and very hard to get rid off. COMPILE DATABASE fixed the problem, though.

Anyway, we're talking here about users reporting bugs. What if the fellow developer finds bugs and tries to report them to the team member?
Lots of times I have problems trying to tell my colleagues where the bug lies. In my opinion bugs report coming from the developer is better because it usually gives you precise piece of code that needs to be fixed.

Thanks to everyone for the input in this thread.

>I like them - as long as they're done properly. I have an application that keeps track of these - and the error routine(s) in my other applications will generate new records for it (including a screen shot). I've setup some required fields so that 90% of the time I get what I need - but when a user says something like "I clicked my mouse on the screen and it broke.."...that's completely useless. Anyway I think its very important to keep a record of these things so you can see what's happening the most, which is most critical to fix - etc.
>
>>Hi everybody,
>>
>>We discussed this issue with my colleague today on the way to work...
>>
>>I have no problems if somebody will tell me my software has bugs and demonstrate them to me. In fact, I appreciate this very much. Sometimes these bugs are really hard to reproduce, this would probably be exhausing...
>>
>>But I think lots of developers hate being told that their software has bugs. Instead of thanking and making a fix they would start to hate the person reporting them. I think, it's the wrong attitude.
>>
>>So, I'm curious, how do you personally take bug reports?
>>
>>Thanks.