ActiveX Data Objects --- This is a key part of Microsoft's data access strategy. ADO provides a COM Object to access any data source which has an OLE-DB provider. Also, there is an ODBC OLE-DB provider which you can use for any data source with an ODBC driver, until a native OLE-DB provider is written for it.
Using ADO shows a code sample within Visual FoxPro.
ADO is the evolution of Rd O and Da O.
Sometimes an SQL-Server stored procedure which is supposed to return an ADO record set works fine in the Query Analyzer, but doesn't return anything when used to create an ADO record set. If it's a procedure that creates intermediate temporary files, adding SET NOCOUNT ON early in the procedure shuts off the notification of how many records got selected in each step, and results in the ADO record set being returned without any problem. -- Ilmar Waldner
Regarding Visual FoxPro, the
vfpcom.dll has methods to move between ADO Recordsets and VFP cursors, and surface ADO events.
See: VFPCOM Utility for Visual FoxPro, to download the utility.
The translation between recordsets and cursors has some limitations. You get the source code and thus more flexibility with Ken Levy's rs2dbf.EXE and dbf2rs.EXE functions in the downloadable files from Microsoft FTP: ftp://ftp.microsoft.com/Softlib/MSLFILES/.
Under VFP 8, you should use the new Cursor Adapter to connect to ADO as it does the translation to a Fox cursor automatically.
Is there a HowTo for Cursor Adapter?
See also: Exam 70-155 ADO
Category Data Category ADO Category Exam 70-155 Hot Topic
( Topic last updated: 2005.09.15 09:03:44 AM )