>Bob:
>
>I've been undecided on which way to go for client server development. I've done some reading and experiementing with ADO and I like what I see. What would be really nice if we could subclass ADO objects.
>
>To leverage the strengths of VFP you are going to have to convert ADO RS to cursors. I'm wondering if it is worth the additional overhead? I mean, is the VFP cursor technology that more flexiblle than ADO? If the answer is yes, than VB may better for client server development.
>
>I guess we'll know the true strenghts of VFP as it develops into the future.
>
>Charlie

I've have just about decided that I don't need cursors either. The VFPCOM rs2cursor and cursor2rs routines are buggy. I wrote one of my own to get around them but I've only used it once.

Think about it, what do we do with cursors on the user interface side? Most of the time we're using them to populate a list box, some text boxes, or (God Forbid!) a grid. If I'm poplulating a list box, I find it just as easy to use the additem method and populate control on the fly from the recordset.

Times change, so must we.