> > >> but with this app, I am now giving CA's a go. (Thank you Bernard for your excellent series in the articles section of this site.)
> > >
> >
> >
> > Hey Ken
> >
> > With CA's all you have to do is change the connection type from ODBC to OLEDB and the CA will do the rest. You will still have cursors and will still be able to bind your data to forn objects.
> >
> > If you need any more info please don't hesitate to ask.
> >
> > Bernard
>
> Bernard,
>
> Your articles have already proved most beneficial. (To anyone trying to learn about CA's, go directly to the articles section and look up Bernard's "Simple CA Tutorials".)
>
> I have already played with both OLDDB and ODBC variants and it is surprisingly simple. Thanks very much for the invitation for more help - I will most definately keep that in mind.
>
> Have you played with the ADO recordset yet? I know that I can take a recordset and turn it into a cursor, but what I am looking at is the possibility of running directly from the RS - without the cursor. It is a bit of a departure from the standard VFP cursor mindset, but I want to go there next.
>
> Ken
> You shall know the truth - and the truth shall set you free. (John 8:33)

Hi Ken

I have hated the ADO recordset from the very first time it came out in VB3. That should tell you enough. Also if I wanted to use it, I had to throw away too many VFP functions like Seek, Scan etc to name a couple. Now that we have CA's, I am not indifferent to using OLEDB. Except that I mostly work with SQL server now and ODBC works splendidly for me.

It is fast, I can use SPT for adhoc calls or queries and it returns me cursors. If I ever needed to go to VFP data remotely only then would I consider OLEDB. And even then I would only use cursors so all i'd lose would be SPT.