oConn.Open "Provider=ADSDSOObject;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see: Microsoft OLE DB Provider for Microsoft Active Directory Service
To view Microsoft KB articles related to Data Link File, click here
oConn.Open "Provider=Advantage OLE DB Provider;" & _
"Data source=c:\myDbfTableDir;" & _
"ServerType=ADS_LOCAL_SERVER;" & _
"TableType=ADS_CDX"
For more information, see: Advantage OLE DB Provider (for ADO)
oConn.Open "Provider=IBMDA400;" & _
"Data source=myAS400;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see:
oConn.Open "Provider=SNAOLEDB;" & _
"Data source=myAS400;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see: ConnectionString Property
To view Microsoft KB articles related to OLE DB Provider for AS/400 and VSAM, click here
For Data Warehouse
oConn.Open "Provider=Commerce.DSO.1;" & _
"Data Source=mscop://InProcConn/Server=mySrvName:" & _
"Catalog=DWSchema:Database=myDBname:" & _
"User=myUsername:Password=myPassword:" & _
"FastLoad=True"
' Or
oConn.Open "URL=mscop://InProcConn/Server=myServerName:" & _
"Database=myDBname:Catalog=DWSchema:" & _
"User=myUsername:Password=myPassword:" & _
"FastLoad=True"
For Profiling System
oConn.Open "Provider=Commerce.DSO.1;" & _
"Data Source=mscop://InProcConn/Server=mySrvName:" & _
"Catalog=Profile Definitions:Database=myDBname:" & _
"User=myUsername:Password=myPassword"
' Or
oConn.Open _
"URL=mscop://InProcConnect/Server=myServerName:" & _
"Database=myDBname:Catalog=Profile Definitions:" & _
"User=myUsername:Password=myPassword"
For more information, see: OLE DB Provider for Commerce Server, DataWarehouse, and Profiling System
To view Microsoft KB articles related to OLE DB Provider for Commerce Server, click here
- OLE DB Provider for DB2 (from Microsoft)
For TCP/IP connections
oConn.Open = "Provider=DB2OLEDB;" & _
"Network Transport Library=TCPIP;" & _
"Network Address=xxx.xxx.xxx.xxx;" & _
"Initial Catalog=MyCatalog;" & _
"Package Collection=MyPackageCollection;" & _
"Default Schema=MySchema;" & _
"User ID=MyUsername;" & _
"Password=MyPassword"
For APPC connections
oConn.Open = "Provider=DB2OLEDB;" & _
"APPC Local LU Alias=MyLocalLUAlias;" & _
"APPC Remote LU Alias=MyRemoteLUAlias;" & _
"Initial Catalog=MyCatalog;" & _
"Package Collection=MyPackageCollection;" & _
"Default Schema=MySchema;" & _
"User ID=MyUsername;" & _
"Password=MyPassword"
For more information, see: ConnectionString Property, and Q218590
To view Microsoft KB articles related to OLE DB Provider for DB2, click here
The Microsoft OLE DB Provider for DTS Packages is a read-only provider that exposes Data Transformation Services Package Data Source Objects.
oConn.Open = "Provider=DTSPackageDSO;" & _ "Data Source=mydatasource"
For more information, see: OLE DB Providers Tested with SQL Server
To view Microsoft KB articles related to OLE DB Provider for DTS Packages, click here
oConn.Provider = "EXOLEDB.DataSource" oConn.Open = "http://myServerName/myVirtualRootName"
For more information, see: Exchange OLE DB Provider, Messaging, Calendaring, Contacts, and Exchange using ADO objects
To view Microsoft KB articles related to OLE DB Provider for Exchange, click here
Currently Excel does not have an OLE DB Provider.
However, you can use the ODBC Driver for Excel.
Or use the OLE DB Provider for JET to read and write data
in an Excel workbook.
oConn.Open "Provider=MSIDXS;" & _
"Data source=MyCatalog"
For more information, see: Microsoft OLE DB Provider for Microsoft Indexing Service
To view Microsoft KB articles related to OLE DB Provider for Index Server, click here
oConn.Open "Provider=MSDAIPP.DSO;" & _
"Data Source=http://mywebsite/myDir;" & _
"User Id=myUsername;" & _
"Password=myPassword"
' Or
oConn.Open "URL=http://mywebsite/myDir;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see: Microsoft OLE DB Provider for Internet Publishing and Q245359
To view Microsoft KB articles related to OLE DB Provider for Internet Publishing, click here
For standard security
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\myDb.mdb;"
If using a Workgroup (System Database)
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\mydb.mdb;" & _
"Jet OLEDB:System Database=MySystem.mdw", _
"myUsername", "myPassword"
Note, remember to convert both the MDB and the MDW to the 4.0
database format when using the 4.0 OLE DB Provider.
If MDB has a database password
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\mydb.mdb;" & _
"Jet OLEDB:Database Password=MyDbPassword", _
"myUsername", "myPassword"
If want to open up the MDB exclusively
oConn.Mode = adModeShareExclusive
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\myDb.mdb;"
If MDB is located on a network share
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=\\myServer\myShare\myPath\myDb.mdb"
If MDB is located on a remote machine
- Or use an XML Web Service via SOAP Toolkit or .NET
- Or upgrade to SQL Server and use an IP connection string
If you don't know the path to the MDB (using ASP)
<% ' ASP server-side code
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & Server.MapPath(".") & "\db\myDb.mdb;" & _
%>
This assumes the MDB is in a sub-directory called "db" directory, which has Read/Write permissions for the Web site identity account (e.g. IUSR_XXXXX).
If you don't know the path to the MDB (using VB)
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & App.Path & "\myDb.mdb;" & _
"User Id=admin;" & _
"Password="
This assumes the MDB is in the same directory where the application is running.
For more information, see: OLE DB Provider for Microsoft Jet, Q191754, and Q225048
Note: Microsoft.Jet.OLEDB.3.51 only gets installed by MDAC 2.0. Q197902
Note: MDAC 2.6 and 2.7 do not contain any of the JET components. Q271908 and Q239114
To view Microsoft KB articles related to OLE DB Provider for Microsoft JET, click here
You can also open an Excel Spreadsheet using the JET OLE DB Provider
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\mySpreadsheet.xls;" & _
"Extended Properties=""Excel 8.0;HDR=Yes"""
Where "HDR=Yes" means that there is a header row in the cell range
(or named range), so the provider will not include the first row of the
selection into the recordset. If "HDR=No", then the provider will include
the first row of the cell range (or named ranged) into the recordset.
For more information, see: Q278973
You can also open a Text file using the JET OLE DB Provider
oConn.Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=c:\somepath\;" & _
"Extended Properties=""text;HDR=Yes;FMT=Delimited"""
'Then open a recordset based on a select on the actual file
oRs.Open "Select * From MyTextFile.txt", oConn, _
adOpenStatic, adLockReadOnly, adCmdText
For more information, see: Q262537
oConn.Open "Provider=Microsoft.Project.OLEDB.9.0;" & _
"Project Name=c:\somepath\myProject.mpp"
For more information, see: Microsoft Project 2000 OLE DB Provider Information
To view Microsoft KB articles related to OLE DB Provider for Microsoft Project, click here
oConn.Open "Provider=MySQLProv;" & _
"Data Source=mySQLDB;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see: API - OLE DB and Snippet
WARNING: This OLE DB Provider is considered obsolete by Microsoft!
For Access (Jet)
oConn.Open "Provider=MSDASQL;" & _
"Driver={Microsoft Access Driver (*.mdb)};" & _
"Dbq=c:\somepath\mydb.mdb;" & _
"Uid=myUsername;" & _
"Pwd=myPassword"
For SQL Server
oConn.Open "Provider=MSDASQL;" & _
"Driver={SQL Server};" & _
"Server=myServerName;" & _
"Database=myDatabaseName;" & _
"Uid=myUsername;" & _
"Pwd=myPassword"
For more information, see: Microsoft OLE DB Provider for ODBC
To view Microsoft KB articles related to OLE DB Provider for ODBC, click here
Microsoft OLE DB for Online Analytical Processing (OLAP) is a set of
objects and interfaces that extends the ability of OLE DB to provide
access to multidimensional data stores.
For ADOMD.Catalog
oCat.ActiveConnection = _
"Provider=MSOLAP;" & _
"Data Source=myOLAPServerName;" & _
"Initial Catalog=myOLAPDatabaseName"
For ADOMD.Catalog (with URL)
oCat.ActiveConnection = _
"Provider=MSOLAP;" & _
"Data Source=http://myServerName/;" & _
"Initial Catalog=myOLAPDatabaseName"
For Excel PivotTable
With ActiveWorkbook.PivotCaches.Add(SourceType:=xlExternal)
.Connection = "OLEDB;" & _
"Provider=MSOLAP;" & _
"Location=myServerDataLocation;" & _
"Initial Catalog=myOLAPDatabaseName"
.MaintainConnection = True
.CreatePivotTable TableDestination:=Range("A1"), _
TableName:= "MyPivotTableName"
End With
For more information, see: OLE DB for OLAP, Catalog Object, PivotTable, Connecting Using HTTP
To view Microsoft KB articles related to OLE DB Provider for OLAP Services, click here
oConn.Open "Provider=msdaora;" & _
"Data Source=MyOracleDB;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For more information, see: Microsoft OLE DB Provider for Oracle
To view Microsoft KB articles related to OLE DB Provider for Oracle, click here
For Standard Security
oConn.Open "Provider=OraOLEDB.Oracle;" & _
"Data Source=MyOracleDB;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For a Trusted Connection
oConn.Open "Provider=OraOLEDB.Oracle;" & _
"Data Source=MyOracleDB;" & _
"User Id=/;" & _
"Password="
' OroConn.Open "Provider=OraOLEDB.Oracle;" & _
"Data Source=MyOracleDB;" & _
"OSAuthent=1"
Note: "Data Source=" must be set to the appropriate Net8 name which is known to the naming method in use. For example, for Local Naming, it is the alias in the tnsnames.ora file; for Oracle Names, it is the Net8 Service Name.
For more information, see: Oracle Provider for OLE DB Developer's Guide
oConn.Open "Provider=PervasiveOLEDB;" & _
"Data Source=C:\PervasiveEB"
For more information, see: OLE DB - ADO
The Microsoft OLE DB Simple Provider (OSP) allows ADO to access any data for which a provider has been written using the OLE DB Simple Provider Toolkit. Simple providers are intended to access data sources that require only fundamental OLE DB support, such as in-memory arrays or XML documents.
OSP in MDAC 2.6 has been enhanced to support opening hierarchical ADO Recordsets over arbitrary XML files. These XML files may contain the ADO XML persistence schema, but it is not required. This has been implemented by connecting the OSP to the MSXML2.DLL, therefore MSXML2.DLL or newer is required.
oConn.Open "Provider=MSDAOSP;" & _
"Data Source=MSXML2.DSOControl.2.6"
oRS.Open "http://WebServer/VirtualRoot/MyXMLFile.xml",oConn
For more information, see: Microsoft OLE DB Simple Provider and Q272270
To view Microsoft KB articles related to OLE DB Provider for Simple Provider, click here
oConn.Open "Provider=SQLBaseOLEDB;" & _
"Data source=mySybaseServer;" & _
"Location=mySybaseDB;" & _
"User Id=myUserName;" & _
"Password=myUserPassword"
For more information, see: Books on-line
For Standard Security
oConn.Open "Provider=sqloledb;" & _
"Data Source=myServerName;" & _
"Initial Catalog=myDatabaseName;" & _
"User Id=myUsername;" & _
"Password=myPassword"
oroConn.Open "Provider=sqloledb;" & _
"Server=myServerName;" & _
"Database=myDatabaseName;" & _
"User Id=myUsername;" & _
"Password=myPassword"
For a Trusted Connection
oConn.Open "Provider=sqloledb;" & _
"Data Source=myServerName;" & _
"Initial Catalog=myDatabaseName;" & _
"Integrated Security=SSPI"
To connect to a "Named Instance"
oConn.Open "Provider=sqloledb;" & _
"Data Source=myServerName\myInstanceName;" & _
"Initial Catalog=myDatabaseName;" & _
"User Id=myUsername;" & _
"Password=myPassword"
Note: In order to connect to a SQL Server 2000 "named instance", you must have MDAC 2.6 (or greater) installed.
To Prompt user for username and password
oConn.Provider = "sqloledb"
oConn.Properties("Prompt") = adPromptAlways
oConn.Open "Data Source=myServerName;" & _
"Initial Catalog=myDatabaseName"
To connect to SQL Server running on the same computer
oConn.Open "Provider=sqloledb;" & _
"Data Source=(local);" & _
"Initial Catalog=myDatabaseName;" & _
"User ID=myUsername;" & _
"Password=myPassword"
To connect to SQL Server running on a remote computer (via an IP address)
oConn.Open "Provider=sqloledb;" & _
"Network Library=DBMSSOCN;" & _
"Data Source=xxx.xxx.xxx.xxx,1433;" & _
"Initial Catalog=myDatabaseName;" & _
"User ID=myUsername;" & _
"Password=myPassword"
Where:
- "Network Library=DBMSSOCN" tells OLE DB to use TCP/IP rather than
Named Pipes (Q238949)
- xxx.xxx.xxx.xxx is an IP address
- 1433 is the default port number for SQL Server. Q269882 and Q287932
- You can also add "Encrypt=yes" for encryption
For more information, see: Microsoft OLE DB Provider for SQL Server
To view Microsoft KB articles related to OLE DB Provider for SQL Server, click here
The SQLXMLOLEDB provider is an OLE DB provider that exposes the Microsoft SQLXML functionality through ADO. The SQLXMLOLEDB provider is not a rowset provider; it can only execute commands in the "write to an output stream" mode of ADO.
oConn.Open "Provider=SQLXMLOLEDB.3.0;" & _
"Data Provider=SQLOLEDB;" & _
"Data Source=mySqlServerName;" & _
"Initial Catalog=myDatabaseName;" & _
"User Id=myUserName;" & _
"Password=myUserPassword"
For more information, see: SQLXML 3.0 and A Survey of Microsoft SQL Server 2000 XML Features
To view Microsoft KB articles related to OLE DB Provider for SQL Server via SQLXMLOLEDB, click here
oConn.Open "Provider=ASAProv;" & _
"Data source=myASA"
For more information, see: ASA Programming Interfaces Guide and ASA User's Guide
oConn.Open "Provider=Sybase ASE OLE DB Provider;" & _
"Data source=myASEServer"' Or
oConn.Open "Provider=Sybase.ASEOLEDBProvider;" & _
"Srvr=myASEServer,5000;" & _
"Catalog=myDBName;" & _
"User Id=myUserName;" & _
"Password=myUserPassword"
Where:
- The Sybase ASE OLE DB provider from the Sybase 12.5 client CD
- 5000 is the port number for Sybase.
Note: The Open Client 12 Sybase OLE DB Provider fails to work without creating a Data Source .IDS file using the Sybase Data Administrator. These .IDS files resemble ODBC DSNs.
Note: With Open Client 12.5, the server port number feature finally works, allowing fully qualified network connection strings to be used without defining any .IDS Data Source files.
For more information, see: Opening Sybase databases
Actually there is no OLE DB Provider for Text files. However, you can use the OLE DB Provider for JET to read and write data in Text files. Or you can use the ODBC Driver for Text.
oConn.Open "Provider=Ardent.UniOLEDB;" & _
"Data source=myServer;" & _
"Location=myDatabase;" & _
"User ID=myUsername;" & _
"Password=myPassword"
For more information, see: IBM Using UniOLEDB, Informix Using UniOLEDB 5.2
oConn.Open "Provider=vfpoledb;" & _
"Data Source=C:\vfp8\Samples\Data\myVFPDB.dbc;" & _
"Mode=ReadWrite|Share Deny None;" & _
"Collating Sequence=MACHINE;" & _
"Password=''"
The Visual FoxPro OLE DB Provider is not installed by MDAC 2.x. You must install Visual FoxPro or download the OLE DB Provider
For more information, see: Microsoft OLE DB Provider for Visual FoxPro
To view Microsoft KB articles related to OLE DB Provider for Visual FoxPro, click here.
'Interesting > TIPTECH' 카테고리의 다른 글
| C2 리드유저 (0) | 2007.05.02 |
|---|---|
| .NET Data Providers (3) | 2007.04.25 |
| 쇼핑몰 무한 카테고리 구현 (1) | 2007.04.25 |
| 옥션에서 기회를 잡는 방법, 오픈마켓에서 기회 잡는 법 (0) | 2007.02.26 |
| 오픈마켓 (1) | 2007.02.26 |