>The export you're talking about must be application specific or part of a framework used to build the app. I use my own error handling so I'm not familiar with this export routine. However, my only comment would be that it is not desirable to ask a user to take some action when an error occurs. It should be automatic and opaque to the user other than to let them know somethin ain't right. Where the error information goes should be some location easily accessable to the developer. In your case, maybe it should go to a table locally and emailed to you as well. That way you'll know what happened before the user calls.

I disagree here. Sometimes it is incredibly valuable to have the user type a few comments as to what they were doing when the error occurred. Juts knowing what the environment looked like isn't always enough to debug the problem.