Need example of web.config ConnectionString for Access mdb

A good site for connection strings. One of my favs.

http://www.connectionstrings.com/

Thanks jojo1771, but that's essentially what I had before; I got the same error:
Keyword not supported: 'provider'.

Thanks Sammy1971, but that got a different error message:
Format of the initialization string does not conform to specification starting at index 0.

Both of these error messages point to the line:
Dim cmd As SqlCommand = New SqlCommand(sel, New SqlConnection(GetConnectionString))

I took a wild quess and added a line in the class code for "Imports System.Data.OleDb", but no help.

I'm using code examples that are going against a SQL Server database; obviously, something in these examples is not appropriate for going against an Access database. Here's the whole thing...

In my web.config:

<connectionStrings>
      <remove name="AccessFileName"/>
      <add name="AccessFileName" connectionString="~/App_Data/MyMDB.mdb" providerName="System.Data.OleDb"/>
</connectionStrings>
 

In my Object Data Source class code:

Imports Microsoft.VisualBasic
Imports System.ComponentModel
Imports System.Data
Imports System.Data.SqlClient
Imports System.Data.OleDb

Public Class clsCensusData

    <DataObjectMethod(DataObjectMethodType.Select)> _
    Public Shared Function TestCensusDataList() As IEnumerable
        Dim sel As String = "SELECT * FROM tblCensusData ORDER BY EmpName"
        Dim cmd As SqlCommand = New SqlCommand(sel, New SqlConnection(GetConnectionString))
        cmd.Connection.Open()
        Dim rdr As SqlDataReader = cmd.ExecuteReader(CommandBehavior.CloseConnection)
        Return rdr
    End Function

    Private Shared Function GetConnectionString() As String
        Return ConfigurationManager.ConnectionStrings("AccessFileName").ConnectionString
    End Function

End Class

Thanks again for all your responses

Thanks for all your suggestions. I have since realized:

1) The data retrieval command yik-yak would have to be OleDB yik-yak, not SQL yik-yak, and I can't find any examples of that out there (the things you pointed me to might start out with connnection strings for mdb's, but no related command statements for going against an mdb)  

2) I was trying to postpone the inevitable by using an Access mdb "for prototyping"; I need to swim out of the shallow end of Access and into the deep end of SQL Server

Thanks again for your responses