	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[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!

9.1

reduce redundant data access code

Asked by llj45 in Programming for ASP.NET, Microsoft Visual Basic.Net, SQL Server 2008

Tags: asp.net ado.net vb.net

Hello,
I find myself constantly using the code listed in a web based system which is currently under construction. In the interest of reducing the use of the same code over and over, I wish to develop a class, function or sub or something which can be sent several parameters to do what the repetitive code does now. These parameters would have to include the list of incoming "parameters" to the stored procedure. Probably, there needs to be two different classes or whatever. One class would return the results of SELECT statements. The other class or whatever would return simply the record count or such indicating success from an INSERT, UPDATE or DELETE operation.
The number of parameters going into the class or whatever varies. So, perhaps, an array could be used to transport a flexible number of parameters to the stored procedure.

Perhaps, there are good working examples on the Internet of how to do this work.
I am using ASP.NET 3.5, ADO.NET 3.5 and VB.NET with stored procedures in SQL Server 2008.
I don't need anything really elaborate just help me dramatically reduce the redundant code. So, put the code in one place and call it again and again to work with the database.
Also, SQL datasource control on the aspx page doesn't work for me.
Thanks, LLJ45

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:

           
           
             SAMPLE 1 - SELECT
Dim SprocCommand As New SqlClient.SqlCommand
        Dim SprocConn As String = WebConfigurationManager.ConnectionStrings("RCD").ConnectionString
        Dim dcPlan As New SqlClient.SqlConnection(SprocConn)
        Dim daPlan As New SqlClient.SqlDataAdapter()
        Dim dsPlan As New DataSet
 
        Try
            SprocCommand.CommandType = CommandType.StoredProcedure
            SprocCommand.Connection = dcPlan
            SprocCommand.CommandText = "usp_plan_find_pin"
 
            Call SprocCommand.Parameters.Clear()
 
            'Create and append the parameters for the SELECT command
            Dim parmSSN As New SqlClient.SqlParameter("@SSN", Trim(txtSSN.Text))
            SprocCommand.Parameters.Add(parmSSN)
 
            Dim parmHPHONE As New SqlClient.SqlParameter("@HPHONE", Trim(txtHTelephone.Text))
            SprocCommand.Parameters.Add(parmHPHONE)
 
            Dim parmHZIP As New SqlClient.SqlParameter("@CERTNUM", Trim(txtCertNum.Text))
            SprocCommand.Parameters.Add(parmHZIP)
 
            If dcPlan.State <> ConnectionState.Open Then
                dcPlan.Open()
            End If
 
            daPlan.SelectCommand = SprocCommand
 
            dsPlan.Clear()
            daPlan.Fill(dsPlan)
 
            dcPlan.Close()
 
SAMPLE 2 - INSERT, UPDATE OR DELETE
                    Dim SprocCommand2 As New SqlClient.SqlCommand
                    Dim SprocConn2 As String = WebConfigurationManager.ConnectionStrings("RCD").ConnectionString
                    Dim dcPlan2 As New SqlClient.SqlConnection(SprocConn2)
                    Dim daPlan2 As New SqlClient.SqlDataAdapter()
 
                    ' get the info. needed to display the test
                    SprocCommand2.CommandType = CommandType.StoredProcedure
                    SprocCommand2.Connection = dcPlan2
                    SprocCommand2.CommandText = "usp_plan_save"
 
                    SprocCommand2.Parameters.Clear()
 
                    'Create and append the parameters for the SELECT command
                    Dim parmPIN2 As New SqlClient.SqlParameter("@PIN", Trim(Session("pr_pin")))
                    SprocCommand2.Parameters.Add(parmPIN2)
                    Dim parmID2 As New SqlClient.SqlParameter("@TESTID", Trim(Session("pr_TestID")))
                    SprocCommand2.Parameters.Add(parmID2)
                    Dim parmQuesID2 As New SqlClient.SqlParameter("@DISPLAYNUM", questionID)
                    SprocCommand2.Parameters.Add(parmQuesID2)
                    Dim parmChoiceID As New SqlClient.SqlParameter("@CHOICEID", choiceID)
                    SprocCommand2.Parameters.Add(parmChoiceID)
 
                    If dcPlan2.State <> ConnectionState.Open Then
                        dcPlan2.Open()
                    End If
 
                    SprocCommand2.ExecuteNonQuery()
 
                    dcPlan2.Close()

           
         

20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. abel981,693
2. guru_sami764,050
3. TheLearn...529,355
4. CodeCruiser437,606
5. nmarun431,054
6. GiftsonDJ...363,715
7. aibusines...314,444
8. Juan_Bar...310,594
9. x_com305,780
10. Dhaest300,866
11. jinal294,858
12. CB_Thiru...294,313
13. carlnorrbom258,132
14. davrob60252,917
15. sunithnair237,805
16. DropZone234,070
17. praveenv...232,932
18. prairiedog220,925
19. burakiewicz216,947
20. daveamour215,055
21. Omego2K213,665
22. HainKurt206,459
23. ragi0017205,715
24. angelIII201,692
25. wht1986186,866

1. TheLearn...3,566,817
2. samtran0...2,728,399
3. raterus2,081,290
4. nauman_...1,216,228
5. sammy1...1,193,317
6. Rejojohny1,121,409
7. abel1,016,343
8. mmarinov996,221
9. scolja962,242
10. prairiedog921,362
11. Dhaest793,214
12. guru_sami764,050
13. angelIII759,102
14. Juan_Bar...648,279
15. lem2802634,188
16. AerosSaga600,606
17. TimCottee580,519
18. pratima_...579,106
19. Edwin_C568,753
20. CodeCruiser540,665
21. x_com530,281
22. tusharashah517,701
23. Justin_W489,746
24. strickdd487,968
25. carl_tawn470,356

reduce redundant data access code

Asked by llj45 in Programming for ASP.NET, Microsoft Visual Basic.Net, SQL Server 2008

Tags: asp.net ado.net vb.net

About this solution