#############################################################

'con.Open "Provider=SQLOLEDB; DSN=dvc; Database=dvc; uid=dvc;pwd=dvc"

'con.Open "Provider=SQLOLEDB; Data Source=CLIENT1\VSDOTNET2003; Initial Catalog=dvc; User Id=dvc; Password=dvc"

'For .net use
'con.Open "Provider=SQLOLEDB.1;Persist Security Info=False;User ID=dvc;Initial Catalog=dvc;Data Source=CLIENT1\VSdotNET2003;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=CLIENT1;Use Encryption for Data=False;Tag with column collation when possible=False;Initial Catalog=dvc;"


#############################################################

'Create a connection to the database
Dim objConn
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open connectionString

'Specify a SQL query
const strSQL = "SELECT * FROM TableName"

'Create a Recordset object, populate it with the query results
Dim objRS
Set objRS = Server.CreateObject("ADODB.Recordset")
objRS.Open strSQL, objConn

'Loop through the Recordset
Do While Not objRS.EOF
  do something
  objRS.MoveNext
Loop
------------------------------


Basic DNS-LESS connection example:
DataConn.Open "DBQ=" & Server.Mappath("../_database/database.mdb") & ";Driver={Microsoft Access Driver (*.mdb)};"

This is the other way to do it that should be even better in theory. In my testing I notice a little performance difference. 
    
Accessing the Jet Driver directly connection example for Access 97:

DataConn.Open "Data Source=" & Server.Mappath("../_database/database.mdb") & ";Provider=Microsoft.Jet.OLEDB.3.51;"

Here is an example with Access 2000

DataConn.Open "Data Source=" & Server.Mappath("../_database/database.mdb") & ";Provider=Microsoft.Jet.OLEDB.4.0;"

------------------------------------

he answer, young grasshopper, is in the connection string of your connection object. Create a connection object like usual: 


Dim objConn
Set objConn = Server.CreateObject("ADODB.Connection") 
Then, instead of using a connection string like DSN=pubs or DRIVER={MS SQL-Server};UID=sa;PWD=;DATABASE=pubs;SERVER=myMachine, use the following connection string: 


objConn.ConnectionString = "Provider=ProviderName; Data Source=DatabaseSource; Initial Catalog=DatabaseName; User ID=UserID; Password=Password" 
For SQL:
ProviderName = SQLOLEDB
Data Source = Server Name
Initial Catalog = Database Name


For Access
ProviderName = Microsoft.Jet.OLEDB.3.51
Data Source = Full path to .MDB file


(Note: This only works for ADO 2.0 and up! If you are using an older version of ADO, you will need to upgrade. You can download the latest version of ADO for free at http://www.microsoft.com/data.) 

So, let's look at two examples, one for Access and one for SQL. Say that you had a DSN-less connection string for a SQL database like so: 


DRIVER={MS SQL-Server};UID=sa;PWD=;DATABASE=pubs;SERVER=myMachine 
To connect directly to OLEDB, your connection string would be: 


Provider=SQLOLEDB; Data Source=myMachine; Initial Catalog=pubs; User ID=sa; Password= 
Now, let's look at the Access side. If you had an Access connection string like so: 


DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=c:\inetpub\wwwroot\users.mdb 
To connect directly to OLEDB, your connection string would be: 


Provider=Microsoft.Jet.OLEDB.3.51; Data Source=c:\inetpub\wwwroot\users.mdb 
That's it! Pretty simple, eh?