Sub Openmodule00(varControllerDBname )
dim path, objConn00
path = Server.Mappath("./_dbase/" & varControllerDBname)
strConn00 = "Driver={Microsoft Access Driver (*.mdb)};DBQ=" & path &";u='';p=''"
Set objConn00 = Server.CreateObject("ADODB.Connection")
objConn00.Open (strConn00)
End Sub

To use this download:
1.If you are the user of an application, consult your application documentation for details on how to use the appropriate driver.
2.If you are an application developer using OLEDB, set the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”
◦If you are connecting to Microsoft Office Excel data, add “Excel 14.0” to the Extended Properties of the OLEDB connection string.
3.If you are application developer using ODBC to connect to Microsoft Office Access data, set the Connection String to “Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=path to mdb/accdb file”
4.If you are application developer using ODBC to connect to Microsoft Office Excel data, set the Connection String to “Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=path to xls/xlsx/xlsm/xlsb file”
To remove this download:

This is a generic error triggered by the Access driver that may occur for a variety of reasons, but incorrect permissions is a common cause. More specifically, the ability to work with Microsoft Access databases is implemented through the Microsoft JET Database Engine, which creates various temporary and lock files when it connects to an Access database. The following sections will discuss some of the reasons why this may occur and how to resolve those situations.
Working with 64-bit Systems

Unfortunately there are no 64-bit ODBC drivers, so on 64-bit systems you will have to run your applications in 32-bit mode. To do so, use the following steps:

On the taskbar, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
In the Connections pane, click Application Pools.
Highlight the application pool for your application, then click Advanced Settings... in the Actions pane.
In the Advanced Settings dialog, specify True for Enable 32-Bit Applications.
Click OK to close the Advanced Settings dialog.

Just FYI, this is not a .Net problem. This is an ASP Classic issue.

.Net was built to avoid the sort of aids you are experiencing (web.config connection strings instead of shitty, shitty ODBC etc)