>If you have 'application' level code you probably shouldn't run that code in in the constructor. A constructor should just bring up the object with as few dependencies as possible. Instead consider creating an Initialize() method or something like that that you can externally to set up your connection etc. You can return true or false from that and you can manage that in your application code more easily.
>
>Throwing exceptions will give you that same functionality but I personally think that object instantiation should always work unless there's truly an exceptional failure.

Ok, thanks