Advertisement

05.09.2008 at 08:29AM PDT, ID: 23389733
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

Application unexpectedly dying on a System.Data.SqlClient.SqlDataAdapter.Fill call

Tags: C#
Here's a good one... I've got this code that basically fills a DataTable with some values retrieved from a SqlDataAdapter.  The whole thing is surrounded by try/catch blocks, log4net error logging, i.e. the works.
The application is terminating on the adapter.Fill(table) method.  No exceptions are thrown and I've verified the connection is open and the SQL is good before the call.  Has anyone experienced this yet?

           System.Data.SqlClient.SqlConnection con = null;
            System.Data.SqlClient.SqlDataAdapter adapter = null;
            System.Data.DataTable table = new System.Data.DataTable("RecoveryTestFeed");

            try
            {
                con = new System.Data.SqlClient.SqlConnection(dsn);
                con.Open();

                string sql = string.Format("{0} WHERE {1}", GetQueryStringByFieldName(dsn, strUserID), whereClause.Replace("WHERE", ""));

                adapter = new System.Data.SqlClient.SqlDataAdapter(sql, con);
                adapter.SelectCommand.CommandTimeout = dbTimeOut;

                debug("[SQL] {0}", sql);  // looks good upon inspection

// Application dies at this statement
                adapter.Fill(table);
...
}
catch(System.Exception sx)
{
// This area is never entered
   log.Error("", sx);
}
finally
{
   if(con != null) con.Close();
//The above statement isn't called either
}
Start your free trial to view this solution
Question Stats
Zone: Programming
Question Asked By: sasdevelopment
Solution Provided By: sasdevelopment
Participating Experts: 1
Solution Grade: A
Views: 0
Translate:
Loading Advertisement...
05.09.2008 at 10:01AM PDT, ID: 21534731

Rank: Sage

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
05.09.2008 at 10:19AM PDT, ID: 21534861

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
05.16.2008 at 09:23AM PDT, ID: 21584131

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
20080236-EE-VQP-29 / EE_QW_2_20070628