Bad Network, not throwing catchable exceptions
IT & Infrastructure
1
Posts
1
Posters
1
Views
1
Watching
-
I have an application that runs over a corperate network. Its MFC based . It works fine on most sites , but one site has a shit network , and I am forever getting timeouts. This is being wrongly percieved as my fault . There are erors being thrown that are not passed to my exception handles , even though I have put in as many as I can concieve of. My current thought is to check for network availability prior to any calls. This will not be foolproof. The typical error is SQL timeout . If I catch generate it automatically , the code throws a catchable error when it is starting , but not when the program is up and running . Any ideas ?