>To be honest, I cannot understand this. Its a data tier. I've written one. I'm sure you have. The coolest part about the Cursor Adapater is the builder in the form designer and its integration into the IDE. Beyond that, I still don't "get it", I suppose.
>
>Would you mine sharing those "implications" here?

Sorry for the delay. For one, I can not just create a cursor and make it updatable (which would be faster with larger tables) like a local view (slow creation with larger tables). I can with a CA because no SQL SELECT has to be used to create the initial cursor structure. The performance of data handling in both directions is faster than anything I have created. Another wonderful benefit is its simplicity for new VFP devlopers. Granted it was frustrating for me at first because it is new and documentation was minimal at best, but that will not be the case when 8 is released.

If I had had this object a year ago, I would have cut development time by about 80% on a data migration app I had to create because of some of our overboard security restrictions. I have to transfer 10 of thousands of records from a National Oracle database to a local database every quarter. I have to retrieve the records from one database into a VFP cursor, then send these same records to the local Oracle database. Now I know there is an easier way to directly copy these records from one Oracle DB to another, but no one will grant me the privileges I need to do this because of [non-sensical] security issues. When I get the current app converted to 8 and use these new objects, I will write up a detailed comparison between the way we had to do this in 7 versus using the CA.