>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>Like the MSFlexGrid?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>Yes, but there are others, too - the hierarchical flex grid, the datagrid control (msdatgrd.ocx), and several third party products that bind to ADO recordsets.
>
>But, as you point out, this can make your app pretty ActiveX-heavy. Which is why I still think that dumping the ADO recordset data in and out of a cursor makes more sense, in more cases, for grid manipulation.
One issue is converting ADO FieldTypes to the receiving grid field types. The ADO RS does define fields as character(30) or Numeric. The RS structure designations vary with the source data. Example, RS returns a different type definition for a SQL field having 2 decimals, as compared to the definition it may return for a DBF. Check files (COM/DCOM/OLE) for the ADO Query Analyzer. I am not sure, but I suspect that and ADO connection (Record source) can forward update or insert (or pass data to a stored procedure). I'll try that later tonight.

But in many shops, using PT, the cursor is more or less for navigational support. Typically, Inserts and Update are done one record/row at a time.
HTH