ADO连接数据库字符串大全

Also included are ADO.NET connection strings for each .NET Managed Provider
(SQLClient, OLEDB, and ODBC).

These sample connection strings are compiled
by Carl Prothman, a Microsoft Visual Basic MVP
Enjoy!

　
Table of Contents
ODBC DSN Connections DSN
File DSN

ODBC DSN-Less Connections　 ODBC Driver for AS/400
ODBC Driver for Access
ODBC Driver for dBASE
ODBC Driver for Excel
ODBC Driver for MySQL
ODBC Driver for Oracle
ODBC Driver for Paradox
ODBC Driver for SQL Server
ODBC Driver for Sybase
ODBC Driver for Sybase SQL Anywhere
ODBC Driver for Text
ODBC Driver for Teradata
ODBC Driver for Visual FoxPro

OLE DB Data Link Connections Data Link File (UDL)

OLE DB Data Provider Connections　 OLE DB Provider for AS/400
OLE DB Provider for Active Directory Service
OLE DB Provider for DB2
OLD DB Provider for Internet Publishing
OLE DB Provider for Index Server
OLE DB Provider for Microsoft Jet
OLE DB Provider for ODBC Databases
OLE DB Provider for Oracle (From Microsoft)
OLE DB Provider for Oracle (From Oracle)
OLE DB Provider for Simple Provider

ODBC DSN Connections
Using an ODBC DSN (Data Source Name) is a two step process.

1) You must first create the DSN via the "ODBC Data Source Administrator" program
found in your computer's Control Panel (or Administrative Tools menu in Windows 2000).
Make sure to create a SYSTEM DSN (not a USER DSN) when using ASP.
Note: You can also create the DSN via VB code.

2) Then use the following connection string - with your own DSN name of course.　 ;-)

ODBC - DSN
　
oConn.Open "DSN=AdvWorks;" & _
　　　　　　　　　 "Uid=Admin;" & _
　　　　　　　　　 "Pwd=;

You can also create and use a File DSN. Then use the following ADO Connection string:

ODBC - File DSN
　
oConn.Open "FILEDSN=c:\somepath\mydb.dsn;" & _
　　　　　　　　　 "Uid=Admin;" & _
　　　　　　　　　 "Pwd=;"

For more information, see: About ODBC data sources and
How to Use File DSNs and DSN-less Connections

Note: The problem with DSN is that Users can (and will) modify them (or delete by mistake),
then your program won't work so well... So it's better to use a DSN-Less or OLE DB Provider
connection string with a Trusted Connection if possible!

ODBC DSN-Less Connections
ODBC Driver for AS/400
　
oConn.Open "Driver={Client Access ODBC Driver (32-bit)};" & _
　　　　　　　　　 "System=myAS400;" & _
　　　　　　　　　 "Uid=myUsername;" & _
　　　　　　　　　 "Pwd=myPassword;"

For more information, see:　 A Fast Path to AS/400 Client/Server

ODBC Driver for Access
　
For Standard Security:

oConn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
　　　　　　　　　 "Dbq=c:\somepath\mydb.mdb;" & _
　　　　　　　　　 "Uid=Admin;" & _
　　　　　　　　　 "Pwd=;"

If you are using a Workgroup (System database):

oConn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
　　　　　　　　　 "Dbq=c:\somepath\mydb.mdb;" & _
　　　　　　　　　 "SystemDB=c:\somepath\mydb.mdw;", _
　　　　　　　　　 "admin", ""

If MDB is located on a network share:

oConn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
　　　　　　　　　 "Dbq=\\myServer\myShare\myPath\myDb.mdb;"

For more information, see: Microsoft Access Driver Programming Considerations

ODBC Driver for dBASE
　
oConn.Open "Driver={Microsoft dBASE Driver (*.dbf)};" & _
　　　　　　　　 "DriverID=277;" & _
　　　　　　　　 "Dbq=c:\somepath;"