good stuff Bindu!

it's similar to what I have developed over the last few years - but with one difference: I don't trust users any more to tell me the important stuff!

I show a similar message to yours, but rather than Err.Description I use a special module to convert it to something that is more meaningful to non-programmers, and save this info (and any extra info that is relevant) to a log file, and send a copy of the info by email (using any available method - SQL Server/Outlook etc).

I also have a retry button (a some errors are time limited, or something that can be fixed by the user), and if apt an ignore button.


ooh, just in time! I haven't got any error emails since my job moved temporarily, but one has just arrived, so heres some sample output (@ is used to mask the sensitive stuff!):
Code:
** Message to user -

(18456)
Login failed for user '@@@@'.

ERL=11880

Database     		:			

Time of sending    	:	23/10/2003 09:59:26

Source procedure   	:	@@@@@@@ Editor - Login
(Exit=E&xit,Username = @@@)
Procedure variables: 

EXE path\name     	:	@@@@@@@ Editor
EXE date or version	:	01/10/2003 10:27:16

User logged in    	:	@@@

Error number 		:	3146
** Last SQL -


** MS Office info:
Excel:     	Excel.Application.9
Word:      	Word.Application.9
Outlook:   	Outlook.Application.9
Access:    	Access.Application.9

** Mapped Drives:
...

** ODBC (USER DSN's): 
...
(SYSTEM DSN's)
...
(Drivers):
...

** Application Registry Settings   - HKEY_CURRENT_USER\Software\@@@\@@@@ Editor
	\@@@@@
As you can see, I put lots of information in by default (most of my programs use databases and/or MS Office), and I have a "Procedure variables" section, so each procedure can specify more info if appropriate.

Anyway! I hope that this helps anyone who is planning to implement an error handling strategy.