Yes, Al, you're right - it has a FOR...NEXT or something, but I meant you can't use any of VFP's table-oriented commands (such as Replace All and such). If he'll use ODBC he'll end having local cursors which can be manipulated as regular tables.
Ah, one more thing, and I think this is THE reason: one can bind a grid to a cursor, but cannot bind a grid to an ADO recordset, unless that recordset is iterated and converted into a cursor first. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Allen Sent: Tuesday, June 08, 2010 3:49 PM To: [email protected] Subject: RE: ADO and VFP I thought ADO had its own scan or go next or something like that. Al -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Grigore Dolghin Sent: 08 June 2010 14:39 To: [email protected] Subject: RE: ADO and VFP I would _strongly_ suggest to use ODBC, not ADO. One of the reasons is ADO returns recordsets, which you cannot SCAN...ENDSCAN, for example. [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
