For more information, see: HOWTO: Use Data Link Files with ADO
Note: Windows 2000 no longer contains the "New | Microsoft Data Link" menu anymore. You can add the Data Link menu back in the menu list by running the "C:\Program Files\Common Files\System\Ole DB\newudl.reg" reg file, then right-click on the desktop and select "New | Microsoft Data Link" menu. Or you can also create a Data Link file by creating a text file and change it''''s file extension to ".udl", then double-click the file.
OLE DB Provider Connections OLE DB Provider for AS/400
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 "OLE DB Provider for Microsoft Jet"
'''' Then open a recordset based on a select on the actual file oRs.Open "Select * From MyTextFile.txt", oConn, adOpenStatic, adLockReadOnly, adCmdText
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: Connecting to an Oracle Database (Note, if you get a Logon dialog, then click Cancel, then perform a one-time free signup with Oracle''''s TechNet system)
OLE DB Provider for Simple Provider
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.