Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.InvalidOperationException: The ConnectionString property has not been initialized.

Source Error: 


Line 23:             dbCommand.Connection = dbConnection
Line 24: 
Line 25:             dbConnection.Open
Line 26:             Dim dataReader As System.Data.IDataReader = dbCommand.ExecuteReader(System.Data.CommandBehavior.CloseConnection)

Function GetTeams() As System.Data.IDataReader
            Dim connectionString As String = _
                ConfigurationSettings.AppSettings("connectionstring")
            Dim dbConnection As System.Data.IDbConnection = New System.Data.OleDb.OleDbConnection(connectionString)

Sub Page_Load()
        Teamlist.Datasource = getteams
        teamlist.databind()
    End Sub

        Function GetTeams() As System.Data.IDataReader
            Dim connectionString As String = _
                ConfigurationSettings.AppSettings("connectionstring")
            Dim dbConnection = ConfigurationSettings.AppSettings("connectionstring")

            Dim queryString As String = "SELECT [Teams].[TeamID], [Teams].[TeamName], [Teams].[Notes] FROM [Teams]"
            Dim dbCommand As System.Data.IDbCommand = New System.Data.OleDb.OleDbCommand
            dbCommand.CommandText = queryString
            dbCommand.Connection = dbConnection

            dbConnection.Open
            Dim dataReader As System.Data.IDataReader = dbCommand.ExecuteReader(System.Data.CommandBehavior.CloseConnection)

            Return dataReader
        End Function

<?xml version="1.0" encoding="UTF-8" ?>

<configuration>

    <!--

         The <appSettings> section is used to configure application-specific configuration
         settings.  These can be fetched from within apps by calling the
         "ConfigurationSettings.AppSettings(key)" method:

         <appSettings>
            <add key="connectionstring"
                value="Provider=Microsoft.Jet.OLEDB.4.0; Ole DB Services=-4;
                        Data Source=C:\begaspnet11\wroxunited\database\wroxunited.mdb"/>
         </appSettings>

    -->

    <system.web>

        <!--

            The <sessionState" section is used to configure session state for the application.
            It supports four modes: "Off", "InProc", "StateServer", and "SqlServer".  The
            later two modes enable session state to be stored off the web server machine -
            allowing failure redundancy and web farm session state scenarios.

            <sessionState mode="InProc"
                          stateConnectionString="tcpip=127.0.0.1:42424"
                          sqlConnectionString="data source=127.0.0.1;trusted_connection=true"
                          cookieless="false"
                          timeout="20" />

        -->

        <!--

            The <customErrors> section enables configuration of what to do if/when an
            unhandled error occurs during the execution of a request.  Specifically, it
            enables developers to configure html error pages to be displayed in place of
            a error stack trace:

            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
               <error statusCode="403" redirect="NoAccess.htm"/>
               <error statusCode="404" redirect="FileNotFound.htm"/>
            <customErrors>

        -->

        <!--

            The <authentication> section enables configuration of the security authentication
            mode used by ASP.NET to identify an incoming user.  It supports a "mode"
            attribute with four valid values: "Windows", "Forms", "Passport" and "None":

            The <forms> section is a sub-section of the <authentication> section,
            and supports configuring the authentication values used when Forms
            authentication is enabled above:

            <authentication mode="Windows">

                    <forms name=".ASPXAUTH"
                           loginUrl="login.aspx"
                           protection="Validation"
                           timeout="999999" />

             </authentication>

        -->


        <!--

            The <authorization> section enables developers/administrators to configure
            whether a user or role has access to a particular page or resource.  This is
            accomplished by adding "<allow>" and "<deny>" sub-tags beneath the <authorization>
            section - specifically detailing the users/roles allowed or denied access.

            Note: The "?" character indicates "anonymous" users (ie: non authenticated users).
            The "*" character indicates "all" users.

            <authorization>
               <allow users="joeuser" />
               <allow roles="Admins" />
               <deny users="*" />
            </authorization>

        -->

    </system.web>

</configuration>