|
}
MDAC, or even Microsoft Information Access Components, occurs as class action of Microsoft technologies that interact together as a framework that allows programmers the uniform & comprehensive way of getting applications for accessing well-nigh any information store. These are processed higher of various components: Active X Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC). There use at times been many deprecated components likewise, like a Microsoft Jet Database Engine, MSDASQL, and Remote Data Services (RDS). A bit of components stand too turn into obsolete, such as a previous Data Access Objects API and Remote Data Objects.
A foremost version of MDAC was freed within August 1996, & depending on datthe from either statements from Microsoft wwhen supplementary of the construct so a have-alone program and got there is no far flung distribution method, though late Microsoft freed upgrades to MDAC as web-based redistributable packages. At length, down the road versions were integrated sustaining Microsoft Windows and in MDAC Two.Octet SP1 it ceased offering MDAC as a redistributable pack. Throughout its history MDAC has been a subject of many security flaws, which lead to attacks like an escalated privileges attack, although the vulnerabilities were typically fixed around later on versions & fairly promptly. A todays version is Deuce.Eight service pack 1, but a product has got numerous different versions & numerous of its components keep close at h& been deprecated and replaced by fresh Microsoft technologies.
Architecture
A latest version of MDAC (Deuce.Eight) consists of many interacting components, a lot of which are then Windows specific except for ODBC (which is available on many platforms). MDAC architecture can be deem trine shells: the programming interface layer, consisting of ADO and ADO.NET, a database access layer developed by database vendors such as Oracle and Microsoft (OLE DB, .NET managed providers and ODBC drivers), and the database itself. These component shells come a lot mass produced available to applications through the MDAC API. A Microsoft SQL Server Network Library, a proprietary access method specific to Microsoft SQL Server, is besides involved in the MDAC. Developers of Windows applications come encouraged to utilize Fuss or even Stir.NET for information access, a advantage existence that users of the applications programme are non strained in their guide of database architecture except that it should become supported by MDAC. Naturally, developers however keep around a selection of writing applications which directly access OLE DB & ODBC.
Microsoft SQL Server Network Library
A Microsoft SQL Server Network Library (as well referred to as Net-Lib) is utilized per Microsoft SQL Server to page through & write information utilizing numbers of different network protocols. Though Net-Lib is specific to the SQL Server, Microsoft includes it using MDAC. A SQL Server utilizes a Open Information Services (ODS) library to communicate using Net-Lib, which interfaces directly by having a Windows NT operating system line's Win32 subsystem. a SQL Server Network Library is controlled through the have of a Client Network Utility, which is bundled by using the SQL Server.
Apiece Net-Lib supported network protocol has the separate driver (does'nt to exist as confused by using the device driver), and has trend lines for the session layer in its protocol stack. There are ii general types of Net-Lib: a primary & a secondary. the primary Net-Lib consists of a Extr Socket Net-Lib & a Shared Memory Net-Lib, when there are many secondary Net-Libs, including TCP/IP and named pipes network libraries (named pipes come the method of communicating using more processes vithe a body-persistent pipeline that is given an identity). A Microsoft OLE DB Provider for SQL Server (SQLOLEDB) communicates via primary Net-Libs.
A Extr Socket Net-Lib deals by using inter-computer communications & coordinates a secondary Net-Libs — though a TCP/IP secondary Net-Lib is an exception therein it calls on the Windows Socket 2 API directly. A Banyan VINES, AppleTalk, Servernet, IPX/SPX, Giganet, & RPC Net-Libs were dropped from either MDAC Two.Fivesome ahead. A Network Library router got a job of managing wholly these protocols, nonetheless okay, sole a known as pipes secondary Net-Lib is managed per router. A Very Socket Net-Lib as well handles data encryption via the utilize of the Windows SSL API.
A Shared Memory Net-Lib, but then, manages modems between multiple cases of SQL Server that survive in a single computer. It utilizes the shared memory area to communicate between the processes. This is inherently locate; no want for informatiin encyption between cases of SQL Server that survive on of these computer when a operating rules doesn't allow any more run access to the cases' locality of shared out memory.
Net-Lib is as well suspire to trend lines the impersonation of a logged within user's security context for protocols that trend lines attested modems (known as sure modems). This allows Net-Lib to provide an integrated logon authentication mechanism via a have of Windows Authentication. Windows Authenticatiin is non supported on Windows 98 or even Windows Us.
OLE DB
OLE DB (also known as OLEDB or even OLE-DB) allows MDAC applications access to different types of data stores in the uniform manner. Microsoft has utilized this technology to separate a application from either a information store that it needs to access. This was done because different applications want access to different types & sources of information, & don't necessarily want to understand training access technology-specific functionality. A technology is conceptually divided into consumers & providers. A consumers come a applications that require access to a information, & the provider is the package component that exposes an OLE DB interface through the have of the Component Object Model (or COM).
OLE DB is the database access interface technology utilized by MDAC. OLE DB providers may be created to access such elementary information places as a document or even spreadsheet, through to such complex databases when Oracle and SQL Server. Even so, because different information store technology potty use at times different capabilities, OLE DB providers might not implement each imaginable interface available. A capabilities that come available come implemented through a have of COM objects - an OLE DB provider might map the information store technology's functionality to the particular COM interface. Microsoft calls a accessibility of an interface to become "provider-specific" when it might not become applicable based on the database technology taking part. In addition, still, providers can besides augment the capabilities of a information store - these capabilities come referred to as services inside Microsoft idiom.
A Microsoft OLE DB Provider for SQL Server (SQLOLEDB) is the OLE DB provider that Microsoft will bring for the Microsoft SQL Server from version 6.Quintuplet upwards. Based on data from Microsoft, SQLOLEDB is "the primary focus of future MDAC feature enhancements [and] will be available on the 64-bit Windows operating system."
ODBC
Open Database Connectivity (ODBC) is the native interface that is accessed across a programming language (usually C) that can produce calls into the native library. Around MDAC this interface is defined as a DLL. The separate module or even driver is needed for both database that must exist as accessed. A functions in the ODBC API come implemented by these DBMS-specific drivers. A driver that Microsoft will bring within MDAC is known when a SQL Server ODBC Driver (SQLODBC), & (as a title implies) is designed for Microsoft's SQL Server. It supports SQL Server v6.Pentad & upwards. ODBC allows software to have SQL requests that will access databases while forgoing getting to understand a proprietary interfaces to the databases. It handles a SQL asking & converts it into a asking that the single database body sees.
ADO
Active X Data Objects (ADO) is a high level programming interface to OLE DB. It utilizes the hierarchal object model to allow applications to programmatically create, retrieve, update and delete data from sources supported by OLE DB. Flurry consists of the series of hierarchic COM-depending objects & collections, an object that acts as a container of several more objects. The software engineer might directly access Stir objects to manipulate information, or even could send an SQL query to the database via several Stir mechanisms. Bustle is processed higher of nine objects & quadruplet collections.
A collections come:
Fields: This collection contains the placed of Field objects. the Collection may be utilized witharound either the Recordset object or even in a Record object. Inside the Recordset object, apiece of the Field objects that produce higher the Fields collection corresponds to a column therein Recordset object. Inside a Record object, a Field may be an absolute or even even proportional Address that points into the tree-structured namespace (utilized for semi-structured information providers prefer the Microsoft OLE DB Provider for Internet Publishing) or as a information to the the default Stream object associated thereupon Record object. # Properties: An object might develop other than of these Property object, which are then contained in the object's Properties collection. # Parameters: The Comm& object may stand many Parameter commands to vary its predefined behaviour, and for each one of the Parameter objects come contained in the Command object's Parameters collection # Errors: Completely provider created errors come passed to the collection of Error objects, spell the Errors collection itself is contained within a Connection object. Whenever an Fuss operation creates an error, the collection is cleared & a newly class action of Error objects come created in the collection.
A objects come:
Connection: A connection object is Hustle's connection to the information store via OLE DB. A connection object places info just about a session & will bring methods of connecting to the information store. When the select few information places keep close at hand different methods of establishing a connection, a select few methods might not become supported in the connection object for particular OLE DB providers. The connection object connects to the information store utilizing its 'Open' method by owning a connection string which specifies the connection as a names of key value pairs (for instance: "Provider='SQLOLEDB';Data Source='TheSqlServer'; Initial Catalog='Northwind';Integrated Security='SSPI';") . A run of which must identify a nature and severity of information store connection that a connection object takes. This must exist as either:
* an OLE DB provider (e.g. SQLOLEDB), using the syntax "provider="
* the computer filename, using the syntax "file name="
* the remote provider & server (watch RDS), using the syntax "Remote provider=" and "Remote server="
* an absolute URL, using the syntax "URL=" # Command: When a connection object establishes a session to the information source, videos come sent to the information provider via the command object. A command object could send SQL question directly to the provider through the utilise of the CommandText property, send the parameterised question or even stored procedure through the use of the Parameter object or even Parameters collection or even start a interrogation & go to the resolutions to a dataset object via the Execute method. There are many more methods that may be utilized in a Command object on to more objects, like the Stream, RecordSet or even Connection objects. # Recordset: The recordset is the group of records, & may either came from either a base table or even when the symptom of a question to the table. the RecordSet object contains a Fields collection & the Properties collection. , or even through the have of dealing:
Quick: A recordset is locked using the adLockOptimistic or even adLockPessimistic lock. A information is updated at a information source when a record is changed & a Upgrade method is known as.
Load: A recordset is locked utilizing adLockBatchOptimistic & from each one instance Upgrade is known as the information is updated around a irregular buffer. Eventually, once UpdateBatch is known as a information is wholly updated back at a information source. This has the benefit of it wholly existence liquidate memory, & whenever a condition occurs so UpdateCancel is known as & a updates are non sent to the information source
Dealing: In case a OLE DB provider allows it, transactions can be used. To run a dealing, a software engineer invokes a BeginTrans method & does a mandatory updates. Whilst it is tons done, a software engineer invokes a CommitTrans method. RollbackTrans may be invoked to cancel any changes manufactured within a dealing & rollback a database to the state before the dealing began # Record: This object is 1 record in the database, and contains the fields collection. The RecordSet consists of the collection of Record objects. # Stream: Water, primarily utilized within the RecordSet object, occurs as means of reading & writing water of bytes. , to send commands to an OLE DB provider alternatively to the CommandText object & to contain the contents of a binary star or even document.
Parameter: the parameter occurs as means of altering the behaviour of the most commin piece of functionality, e.g. a stored procedure may keep close at hand different parameters passed thereto based on what needs to exist as done - which are actually known as parameterised commands. # Field: Apiece Record object contains several fields, & the RecordSet object has the corresponding Field object besides. A RecordSet object's Field object corresponds to the column in the database table that it references. # Property: This object is specific to a OLE DB provider & defines an ability that the provider has implemented. The property object may be either the built-constitutional property — these are the swell defined property implemented by Flurry already & so just can't exist as altered — or even can be a dynamic property — defined per underlying information provider & may be changed # Error: Whilst the OLE DB provider error occurs during a utilise of Stir, an Error object is created in the Errors collection.
ADO.NET
ADO.NET is the latest version of ADO (after ADO 2.8, now often referred to as ADO Classic) and is part of the MDAC 2.8 stack alongside classic ADO. These are built in Microsoft .NET. Though periodically seen as an evolutionary step higher from either Bustle, a few fundamental structural changes were processed by Microsoft. Hustle.Nett diarrhethe across a .Nett Managed Provider, the limited version of an OLE DB provider specifically intentional for .NET. the object structure is no yearn built around a Recordset object. Instead the Dataset object is utilized to contain information gathered from either multiple sources. This is transparent to the software engineer. Unlike a old ADO Recordset, a Dataset's project allows for staccato information. Conceptually, the Dataset object may be seen as the little inside-memory relational database around its have perfect that allow manipulation of information in any counsel (the Recordset was a forward-lone reader). Sequentially to propagate changes back into a database, a Dataadapter object is utilized that transfers information from either between a information source & the DataSet object. Cursors were also deprecated inside Stir.NET, existence replaced using the Datareader object, which is utilized to with efficiency run the big names of outcomes of these record at one time while forgoing storing the two.
Deprecated & obsolete components
MDAC occurs as high-pressure evolving component framework. Per se, there stand been many components that were antecedently section of it however keep around since been deprecated or even flushed completely from either a framework.
Microsoft Jet Database Engine and JRO
Jet stands for Joint Engine Technology & was the database engine used for Microsoft Access, Microsoft Exchange Server and Visual Basic. Jet was section of the Relational Database Management System (RDBMS) and offered one interface that other software package can apply to access Microsoft databases. Jet as well provided trend lines for security, referential integrity, transaction processing, indexing, record, page lockup & information replication. Around late versions of Jet, a engine was reach do SQL queries, store character data inside Unicode format, create views, and allowed bi-directional replication by using a Microsoft SQL Server. It has since been superseded by MSDE.
There were trinity modules to Jet. A single was a Native Jet ISAM Driver, the Coal-black dynamic link library (DLL) that could directly manipulate Microsoft Access database files (MDB), which was the limited form of an Indexed Sequential Access Method (ISAM) database. A second one of a modules were a ISAM Drivers, DLLs that allowed access to ISAM databases, among the children existence Xbase, Paradox, Btrieve and FoxPro files. A final module was a Information Access Objects (DAO) DLL, DAO allowed programmers access to the Jet engine. It was in essence an object-oriented data language used by Access Basic & Visual Basic application developers to access Jet.
Likewise, a Microsoft Jet OLE DB Provider & Replication Objects (JRO) which allowed replication between Jet information sources was flushed from either MDAC Two.Captain hicks
MSDASQL and Oracle ODBC
A Microsoft OLE DB Provider for even ODBC, or MSDASQL, was an OLE DB provider for letting ActiveX Data Objects access to databases via any ODBC driver. There were many OLE-DB providers supplied by Microsoft (providers available were for the Indexing Service, Active Directory, Jet, SQL Server, Oracle & Internet Publishing), nonetheless unless specified, MSDASQL was a default provider utilized by Fuss. Fallowing MDAC Two.Pentad two a Oracle ODBC driver & MSDASQL supported Oracle 7 & part supported Oracle 8i. Features that were non supported were:
CLOB, BLOB, BFILE, NCHAR, NCLOB, and NVARCHAR2 Oracle datatypes
Unicode trend lines for Oracle 7.x & 8i
multiple client cases of Oracle
nested outer joins
Microsoft deprecated a MSDASQL component for their 64-bit operating systems
Remote Data Services (RDS)
Remote Data Services (RDS) allowed a retrieval of a placed of information from either the server, which the client so altered someway so remand to the server for farther processing
SQLXML
SQLXML was designed for SQL Server 2000, however was deprecated using MDAC Two.Half a dozen. It allowed Microsoft's relational database to exist as viewed by XPath and allowed data to viewable as an XML file. It has nin actually been deprecated however has been flushed from either late versions of MDAC, though Microsoft wash provide it as a downloadable component & may trend lines it on their 64-bit operating systems.
Obsolete components
Many components st& been entirely flushed from either MDAC by Microsoft and come there is no elongated supported. It is:
ESQL/C: Embedded SQL (also referred to as E-SQL or even ESQL/C) occurs as way of utilizing SQL whilst programming inside Ocular C. Microsoft dropped trend lines for this fallowing SQL Server 6.Quint was freed, though it did license occasionally of the ESQL/C dog-instance environment to the company known as Micro Focus, who develops COBOL compilers and information * DAO: DAO, or even Data Access Objects were an object oriented interface created by Microsoft which allowed early versions of Microsoft Access and Visual Basic the Jet database engine. Late (within version Ternary.Little phoebe) it was take a breath to bypass a Jet engine altogether & directly access ODBC data sources. * RDO: Remote Data Objects, or RDO, was the Microsoft technology that allowed for the creation of interfaces that directly turn ODBC. RDO version Deuce.Zero was a final version developed by Microsoft.
DB-Library: a C-depending API that allowed an application to interact by owning SQL Server. It might nin become supported on any product fallowing SQL Server 2000, & there are no added features were added when SQL Server 6.Cinque.
History
Microsoft has freed many versions of MDAC throughout its life. A distribution method has been varied & a feature placed is different for both version.
;MDAC Unity.0
MDAC One.Cypher was foremost freed inside August 1996 .
;MDAC Single.5
MDAC One.Cinque was freed between September 1997 & March 1998, & taking part the supplementary centred distribution mechanism than MDAC One.Nought. It was freed by owning Microsoft Internet Explorer Four.Zero, a Internet Client SDK Four.Cypher & across a Video-ROM given out at the 1997 Professional Developers Conference (PDC). There were quadruplet versions of MDAC One.Five:
MDAC One.5a: downloadable from either Microsoft's website
MDAC One.5b: come by owning Windows NT 4.0 Option Pack
MDAC One.5c: fixed issues sustaining Bustle threading & ODBC Connection Pooling & was distributed via a Microsoft web site. It merely come using a ADO/MDAC runtime components.
MDAC One.5d: come involved using Windows 98 and Internet Explorer 4.0One service pack 1.
MDAC One.Five consisted of:
ODBC Terzetto.5
OLE DB Unity.5
Stir One.5
Remote Information Service Ace.Quint, which superseded a Advanced Information Connector.
This version of MDAC experienced the security flaw that manufactured it vulnerable to the escalated privileges attack. the vulnerability induced systems that got each Two & MDAC installed to give an unauthorised web user the ability to execute husk commands in the 2 technique as a privileged user & apply MDAC to burrow SQL & more ODBC information requests through the public connection to a personal back-prevent network whenever on a multi-homed Internet-connected 2 technique. It as well allowed a user to benefit wildcat access to secured, non-published files on the 2 patterns
;MDAC Two.0
MDAC Two.Cipher was distributed sustaining a Information Access Two.Nought SDK & involved a contents of MDAC One.Quintuplet, a ODBC Three.Quintuplet SDK & a OLE DB Single.Phoebe SDK, & a OLE DB for OLAP Specification; it also experienced involved numerous updates to the core product .
;MDAC Deuce.1
MDAC Two.Single was distributed by owning SQL Server 7.0 & SQL Server 6.Five SP5; MDAC Two.I SP1 was distributed by having Internet Explorer Five; MDAC Two.I SP1a (GA) was distributed by having Microsoft Office 2000, BackOffice 4.5 & Ocular Studio 98 SP3; yet, none one versions of MDAC were freed to the general public via the world wide web. MDAC Two.Ace SP2 was distributed from either Microsoft's web site. A components that were involved sustaining Deuce.Unity were:
Hustle Two.1
RDS Ii.1
OLE DB Deuce.1
a OLE DB Provider for ODBC, SQL Server & Oracle
JRO Ii.1
the Pitchy driver
RDO .
This version experienced security vulnerabilities whereby an ungoverned buffer can allow an elevated privileges attack. This was discovered occasionally period afterwards & it affected MDAC Two.Single, Two.Five & Two.Sise & was addressed within the late patch
;MDAC Deuce.5
MDAC Two.Little phoebe was freed in February 17, 2000 and distributed with Windows 2000, and a MDAC service packs were freed within parallel by having a Windows 2000 service packs. It were too distributed across Microsoft's site. 3 service packs were freed. A components involved by owning Deuce.Pentad were:
Stir Two.5
Fuss MD Deuce.5
ADOX Deuce.5
RDS Deuce.5
OLE DB Deuce.5
numerous OLE DB Providers
JRO Ii.5
ODBC Trey.51
numbers of ODBC drivers
several Sooty drivers .
Many issues were discovered therein version of MDAC. Whenever applying OLE DB Session Pooling, Microsoft COM+ would try to continuously batch & unload OLE DB, & the conflict may arise that caused the OLE DB Session Pooling to do at 100% CPU usage. This was late fixed. Microsoft published the fully listings of bugs fixed within [http://support.microsoft.com/kb/293311 MDAC 2.5 Service Pack 2] & [http://support.microsoft.com/kb/810656 MDAC 2.5 Service Pack 3]. The security vulnerability besides existed (late fixed) whereby an uncurbed buffer around was observed in the SQL Server Driver. This flaw was introduced inside MDAC Two.Pentad SP2.
;MDAC Two.6
MDAC Two.Sextet was freed around September 2000 & was distributed through the web & by using Microsoft SQL Server 2000 MDAC Two.Captain hicks RTM, SP1 (freed June 20, 2001), and SP2 (freed June 11, 2002) were distributed in parallel by using a Microsoft SQL Server 2000 service packs, & can as well exist as downloaded from either a Microsoft site.
Beginning using this version of MDAC, Microsoft Jet, Microsoft Jet OLE DB Provider, & a ODBC Desktop Database Drivers were non involved. Instead, these can be installed manually.
;MDAC Ii.7
MDAC Two.Heptad was freed around October 2001 across Microsoft's web site. The refresh release was issued inside April 2002 across the release of Windows XP & through Microsoft's internet site. Version Two.Sevener was available in U.S. English, Chinese (Traditional and Simplified), German, Japanese, Korean, Brazilian Portuguese, Czech, Danish, Greek, Slovak, Slovenian, Spanish, Finnish, French, Hungarian, Italian, Dutch, Norwegian, Polish, Portuguese, Russian, Swedish, and Turkish. Hebrew and Arabic were only available across Windows XP.
A independent feature vary was trend lines for Microsoft's 64-bit operating system, still trend lines for Banyan VINES was also dropped from either this version of MDAC. There were many known issues
Many security issues were resolved by Microsoft for MDAC Two.Vii. David Litchfield of Next Generation Security Software Ltd reported a security vulnerability that final result because one of a ODBC functions inside MDAC that is utilized to attach to information sources contained an uncurbed buffer. .
;MDAC Two.8
MDAC Two.Octet was freed around August 2003 & distributed using Microsoft Windows Server 2003, when well as in Microsoft's [http://msdn.microsoft.com/data/ Data Access Technologies] internet site. It did non introduce any recently features to the product however fixed the total of bugs & security issues — a reg file (automates changes to a register) was flushed that manufactured the server redo inside an "unsafe" mode whereby a RDS can be exploited to benefit wildcat access to the technique
In Could 23, 2005 Brad Rhodes (Lead Program Manager of Microsoft Information Access Technologies) announced that MDAC Two.Octad SP1 was a endure could have-alone redistributable of MDAC that Microsoft might ship. MDAC is currently an official component of the Microsoft's operating formulas, though it is providing on-going bug & security fixes to antecedently freed versions of the web-distributable version. .
Versions
There are 2 slipway of checking the versiin of MDAC that is installed on a computer. 1 way is via Microsoft's Component Checker program, which compares a value of every installed MDAC DLL to the MDAC file manifest. A 2nd way is to prevent a key HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer in the Windows registry. Microsoft notes that this page can be wrong for versions of MDAC before Ii.Unity once likened by using a versions of the MDAC files installed to the patterns
Notes
Kalen Delaney, "Inside Microsoft SQL Server 2000", Microsoft Click, pp. 70-74.
Prash Shirolkar (Creator); Alyssa Henry (contributor); Stephen Pepitone (Contributor); Acey J. Bunch (contributor), [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/data_mdacroadmap.asp "Data Access Technologies Road Map"], Microsoft Corporation, accessed September 19, 2005.
ibid.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcolfields.asp "Fields Collection"], "ADO 2.8 API Reference", accessed September 19, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcolproperties.asp "Properties Collection"], "ADO 2.8 API Reference", accessed September 19, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcolparameters.asp "Parameters Collection"], "ADO 2.8 API Reference", accessed September 19, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcolerrors.asp "Errors Collection"], "ADO 2.8 API Reference", accessed September 19, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconusingconnectionobj.asp "Using a connection object"], "ADO 2.8 Programmers Guide", accessed September 10, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdproconnectionstring.asp "ADO Connection String"], "ADO 2.8 Programmers Guide", accessed September 10, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconcommandoverview.asp "Command Object Overview"], "ADO 2.8 Programmers Guide", accessed September 10, 2005
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconexploringtherecordset.asp "Examining Data"], "ADO 2.8 Programmers Guide", accessed September 10, 2005.
the to the full names of Fuss methods & properties that allow the examination of information around a recordset may be encountered in [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdobjodbrecpme.asp Microsoft's API documentation]
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconeditingdata.asp "Editing data"], "ADO 2.8 Programmers Guide", accessed September 10, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcondeletingrecords.asp "Deleting records using the Delete method"], "ADO 2.8 Programmers Guide", accessed September 10, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconupdatepersistdata.asp "Updating and Persisting Data"], "ADO 2.8 Programmers Guide", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdcontrxproc.asp "Transaction Processing"], "ADO 2.8 Programmers Guide", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdobjrecord.asp "Record Object"], "ADO 2.8 API Reference", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmscadofordocuments.asp "Records and Streams"], "ADO 2.8 Programmers Guide", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmscstreamspersistence.asp "Streams and Persistence"], "ADO 2.8 Programmers Guide", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdobjparameter.asp "Parameter Object"], "ADO 2.8 API Reference", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdobjfield.asp "Field Object"], "ADO 2.8 API Reference", accessed September 12, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdobjproperty.asp "Property Object"] "ADO 2.8 Programmers Guide", accessed September 13, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconerrorhandling.asp "Error Handling"], "ADO 2.8 Programmers Guide", accessed September 18, 2005.
MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconfieldrelatederrors.asp "Field-Related Error Information"], "ADO 2.8 Programmers Guide", accessed September 18, 2005; & MSDN, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdconfieldrelatederrors.asp "Recordset-Related Error Information"], "ADO 2.8 Programmers Guide", accessed September 18, 2005.
Doug Rothaus & Mike Pizzo, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/adonetprogmsdn.asp "ADO.NET for the ADO Programmer"], MSDN, accessed September 22, 2005.
Microsoft, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/oledb/htm/oledb_deprecated_components.asp Deprecated Components (OLE DB)], retrieved August Five, 2005.
Microsoft, [http://msdn.microsoft.com/data/mdac/default.aspx?pull=/library/en-us/dnmdac/html/data_mdacroadmap.asp#mdac%20technologies%20road%20map%20old_topic5 "Data Access Technologies Road Map", Deprecated MDAC Components], retrieved July 30, 2005; & ''Microsoft [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdrefodbcprovspec.asp "ADO Programmer's Guide" Appendix A: Providers, Microsoft OLE DB Provider for ODBC], retrieved July 30, 2005.
Microsoft, MS KB article 244661: [http://support.microsoft.com/kb/q244661/ INFO: Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider], survive reviewed August 25, 200Four, retrieved August 4, 2005.
Microsoft, [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmscsection2_rds.asp "Remote Data Service (RDS)"], retrieved August 11, 2005.
Microsoft, [http://msdn.microsoft.com/data/mdac/default.aspx?pull=/library/en-us/dnmdac/html/data_mdacroadmap.asp#mdac%20technologies%20road%20map%20old_topic5 "Data Access Technologies Roadmap"], "Deprecated MDAC Components", retrieved August 11, 2005.
Kalen Delaney, "Insider Microsoft SQL Server 2000", Microsoft Click, p65.
Christine Solomon, "Microsoft Office 97 Developer's Handbook", Microsoft Click. pp. 195-200.
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"] : MDAC One.0 & One.I (OLE DB Single.Nought & OLE DB One.I) accessed July One, 2005.
Microsoft, [http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q190463&ID=KB;EN-US;Q190463 "INFO: What are MDAC, DA SDK, ODBC, OLE DB, ADO, RDS, and ADO/MD?"] : A MDAC One.Zero Fold (previous reviewed March 14, 2005), accessed July One, 2005.
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"], accessed July One, 2005.
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"] : MDAC One.Fin, accessed July One, 2005.
Microsoft, [http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q190463&ID=KB;EN-US;Q190463 "INFO: What are MDAC, DA SDK, ODBC, OLE DB, ADO, RDS, and ADO/MD?"] : A MDAC One.Quintet Fold (go reviewed March 14, 2005), accessed July One, 2005.
Microsoft, [http://www.microsoft.com/technet/security/bulletin/fq99-025.mspx Microsoft Security Program: Frequently Asked Questions: Microsoft Security Bulletin (MS99-025)], accessed July 6, 2005.
Microsoft, [http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q190463&ID=KB;EN-US;Q190463 "INFO: What are MDAC, DA SDK, ODBC, OLE DB, ADO, RDS, and ADO/MD?"] : A MDAC Two.Cypher Fold (survive reviewed March 14, 2005), accessed July 6, 2005.
Microsoft, [http://support.microsoft.com/kb/243245/EN-US/ PRB: RDS Handler Error Messages Due to Security Settings] (go reviewed September 30, 2003), accessed July 6, 2005; [http://www.microsoft.com/technet/security/bulletin/MS98-004.mspx Microsoft Security Program: Microsoft Security Bulletin (MS98-004)] : "Unauthorized ODBC Data Access with RDS and IIS" (endure revision: July 17, 1998), accessed July 6, 2005; CVE vulnerability [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-1011 CVE-1999-1011].
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"] : MDAC Two.Cipher, accessed July One, 2005.
Microsoft, [http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q190463&ID=KB;EN-US;Q190463 "INFO: What are MDAC, DA SDK, ODBC, OLE DB, ADO, RDS, and ADO/MD?"] : A MDAC Two.Nought Fold (previous reviewed March 14, 2005), accessed July 6, 2005.
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"] : MDAC Two.Unity, accessed July One, 2005.
Microsoft, [http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CC37D12E-AF4A-46DC-B0CC-8C789FDE2F4BMicrosoft Data Access Components: Security Hotfix for Q329414] (download report); [http://www.microsoft.com/technet/security/bulletin/MS02-065.mspx Microsoft Security Bulletin MS02-06] — originally Microsoft KB article Q329414) — (originally posted November 20, 2002), accessed July 6, 2005.
Christian Koller, [http://www.aspheute.com/artikel/20000327.htm "ADO und MDAC Versionen"] : MDAC Two.Fivesome, accessed July One, 2005.
Microsoft, MS KB article 320700, [http://support.microsoft.com/kb/320700 "OLE DB Session Pooling Causes 100 Percent CPU Usage (MDAC 2.5)"], accessed July 6, 2005.
Microsoft, MS KB article 842272 [http://support.microsoft.com/default.aspx?scid=kb;EN-US;842272 Release manifest for MDAC 2.6 (2.60.6526.3)], accessed July 6, 2005.
Microsoft, MS KB article 271908 [http://support.microsoft.com/kb/271908 MDAC version 2.6 and later do not contain Jet or Desktop ODBC drivers], accessed July 6, 2005.
Microsoft, MS KB article 820754 [http://support.microsoft.com/kb/820754 MDAC 2.6 or later should not be installed on SQL Server 7.0 clusters], accessed July 6, 2005.
Veritas, Document ID: 258144 [http://seer.support.veritas.com/docs/258144.htm VERITAS Backup Exec (tm) 9.0 for Windows Servers should not be installed on a Microsoft SQL Server 7.0 Cluster.]
[http://support.microsoft.com/default.aspx?scid=kb;EN-US;842280 Release manifest for MDAC 2.7 Refresh (2.70.9001.0)]
Microsoft, MS KB article 289573 [http://support.microsoft.com/kb/289573/ PRB: Configuring DSNs with SQL Server Net-Libraries.]
Randall C. Kennedy, [http://www.infoworld.com/articles/tc/xml/01/11/26/011126tcmdac.html "It's not a bug, it's a feature"], InfoWorld.
Microsoft, MS KB article 309398 [http://support.microsoft.com/kb/309398/ SQL Server 2000 installation or local connections fail with "SSL Security error :ConnectionOpen (SECDoClientHandshake())" error message.]
Microsoft, MS KB article 297232 [http://support.microsoft.com/kb/297232/ FIX: Cannot Browse Cubes or Process Mining Model After You Install Analysis Services 2000 RTM.]
Microsoft, MS KB article 311720 [http://support.microsoft.com/kb/311720/ PRB: MDAC Rollback May Fail on Windows 95, Windows 98, and Windows Millennium Edition.]
Microsoft, [http://www.microsoft.com/technet/security/Bulletin/MS02-040.mspx Microsoft Security Bulletin MS02-040 Unchecked Buffer in MDAC Function Could Enable System Compromise (Q326573)].
Microsoft, [http://www.microsoft.com/technet/security/Bulletin/MS03-033.mspx Microsoft Security Bulletin MS03-033 Unchecked Buffer in MDAC Function Could Enable System Compromise (823718)]
Microsoft, [http://www.microsoft.com/technet/security/Bulletin/MS04-003.mspx Microsoft Security Bulletin MS04-003 Buffer Overrun in MDAC Function Could Allow Code Execution (832483)]
Microsoft. MS KB article 818490: [http://support.microsoft.com/kb/818490/ INFO: Handunsf.reg File Has Been Removed in MDAC 2.8 Redist Setup for Security Reasons]
Microsoft. MS KB article 838405: [http://support.microsoft.com/kb/838405/ FIX: "Argument passed to data shaping service was invalid" error after you apply MDAC 2.8]
Microsoft. MS KB article 818489, [http://support.microsoft.com/kb/818489/ INFO: ODBC Administrator Changes in MDAC 2.8].
Brad Rhodes (web log entry), [http://blogs.msdn.com/dataaccess/archive/2005/05/23/421039.aspx The end of the MDAC Redistributable], Might 23 2005, retrieved August 11, 2005; & Microsoft, MS KB article 892854: [http://support.microsoft.com/default.aspx?scid=kb;en-us;892854 "Release strategy for Microsoft Data Access Components"], last updated January 24, 2005, retrieved August 11, 2005.
Acey J. Bunch (April 26, 2005), [http://blogs.msdn.com/dataaccess/archive/2005/04/26/412161.aspx "Introducing SQL Native Client"], MSDN blog entry.
Microsoft. MS KB article 301202, [http://support.microsoft.com/?kbid=301202 How to check for MDAC version], endure updated January 18, 2005, retrieved September 29, 2005.
|
