>I'm launching into a project to move a large set of applications from working against a vfp back end to working against a sql server back end.. and have been looking at cursor adapters as a possible step in that direction.
>
>There are a lot of things I like about CA's: they combine some of the advantages of remote views and SPT. I like the consistent interface to vfp, sql server, and xml data, the fact that I don't need to have dbc's for remote views, the fact that they can call stored procedures, their performance (which seems comparable to SPT)
>
>On the other hand, they are a pain to construct.. even aside from the 255 character property limitation.
>We have a LOT of tables and remote views.
>I've used Mark McCasland's CA builder to easilty create CA objects for the tables..
>But creating them for views is a pain.. and there doesn't seem to be any simple way to adapt Mark's code to handle remote views (which are usually parametrized and sitting in a dbc separate from the tables themselves)..
>


Here is my 2 cents. Use cursor adapters when you need them. In one case we need to supply the SQL dynamically and this is a perfect use of a cursor adapter. Use remote views when they do the job. Just think of it as a new tool.