Nuri,

>When i catch an exception;
>1- application warns the end-user for correction.
>2- application tries to solve the problem by itself.
>3- if it's a server object throws exception in order to let the client handle it by itself.
>
>when i can't catch those exceptions;
>application shuts down immediately, this behaviour is not acceptable for professional applications.

Actually, this is the recommended behavior for Frameworks. With a few exceptions Frameworks don't know enough about what causes an error to decide what to do about it. Some "exceptions" to this rule are data access exceptions, such as concurrency conflicts, and so on. You can catch Framework exceptions by overriding the method that contains the code that causes the exception...for example, SaveDataSet() in a business object method. If an error can't be handled at the Framework or application level then the best thing to do is to shut down the application because the environment has become unstable.

That said, is there a particular exception that is being thrown that you want to catch?

Regards,