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

Yeah that was one of my favorites - seems to elimate a lot of the guess work.

>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.

Well I'd rather hear about an error from a developer than a user. Like you said, usually it's going to give you a better target of where the problem is, and plus there is a chance that the end users don't even know about the problem - and I kinda like users to see as few problems as possible....so should a developer who finds but report it to anyone? Well, IMO - report it in the log, sure, report it to other developers or the project manager, sure - but tell users about it? No way unless is something that's gonna mess up data and users need to know to work around it.