🚀 go-pugleaf

Hi

I have a slight problem with an application which throws an access violation 
very infrequently.  I have been unable to recreate it in the lab, and 
whenever it is reported to me, the reporter has no knowledge of the 
information contained in the access violation window - generally they just 
re-boot and walk away.

Can I trap an access violation in such a way that I can log the detail (eg 
violation at xxxx read of yyyy).  I can't think how to formulate the 
exxception handler, and where to put it so that it would be 
application-wide.  I note with interest that the try/catch block around 
Application->Initialize(); etc in the Project Source .cpp doesn't catch such 
an exception, since the application continues to run (albeit crippled) both 
during and following closure of the exception notification window.  Further, 
any timers continue to fire (as you would expect during the display of a 
form), in this case keeping a watch-dog alibe even though the program has 
effectively ceased functioning.

Many thanks,

Denville.