I've compartmentalized my code as directed by chapter 13 page 461. The only touble I'm having is I've had to change my connection string from "Dim connectionString As String = _
            ConfigurationSettings.AppSettings("ConnectionStrin g")" calling it from the web.config file. I now have to use the direct path "Dim connectionString As String = "Provider=Microsoft.Jet.OLEDB.4.0; Ole DB Services=-4; Data Source=C:\BegASPNET\Wr"& _
     "oxUnited\Database\WroxUnited.mdb". Have I missed something or done something wrong.

ps: error was connection is not available.

Can the file with the vb extension with all the code in it see the connection from the web.config file?


Thanks!
Rich

This is the specific error I'm getting:

Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30451: Name 'ConfigurationSettings' is not declared.

Source Error:



Line 83: Function Dates() As System.Data.IDataReader
Line 84: Dim connectionString As String = _
Line 85: ConfigurationSettings.AppSettings("ConnectionStrin g")
Line 86: Dim dbConnection As System.Data.IDbConnection = New System.Data.OleDb.OleDbConnection(connectionString )
Line 87:


Source File: C:\begaspnet11\wroxunited\default.aspx.vb Line: 85

How do I fix it?

Thanks!
Rich

Once you move your code out of a page class an into a helper class, you have moved it from executing in the scope of the page execution where ConfigurationSettings has context.

In the page you can do this:

foo = ConfigurationSettings.AppSettings.Item("asasasas")

Outside the page, in a helper class I think you can do this:

foo = System.Configuration.ConfigurationSettings.AppSett ings.Item("asasasas")

** HOWEVER! ** In a multi-tier design, you should avoid making a lower tier assume where to find connection data. The data is associated with the application, so provide the connection information to the underlying class from the consuming application. Perhaps my opinion on this is completely wrong and someone else can offer a better suggestion. In my mind, if you are storing the connection information in something application specific then the application should tell the data access class what the connection is. In this case the AppSettings node of the application's configuration file (web.config) contains the connection information.