>>The "cursors" I've been using for years in DE are just results from USE command
>>But dealing with cursors from SQL commands seems more complex than DE "cursors"
>>
>>Now there are just some doubts:
>>Which are the advantages of using SQL, instead of DE cursors?
>>Will I have quicker search ? Is data corruption less likely to happen ?
>
>If you are re-thinking your approach on using DE-cursors/views/Slect-cursors,
>I'd reccommend you take a few H and research cursoradapters.
>There are some white papers / session notes about them...
>
>They are not perfect (see the wiki for some of the not-so-wonderful-aspects)
>they are IMHO the easiest way to abstract data usage in out-of-the-box vfp
> (from backend type over access type as well as support in the design tools).
>
>Other approaches might be Andy Krameks data classes or xCase -
>especially with a fwk supporting xCase or dbcX.
>
>my 0.02 EUR
>
>thomas
I agree with Thomas - if you're just starting a new form, the Cursor Adapters may be easier to work with and give more flexibility than views.
If it's not broken, fix it until it is.
My Blog