What does adding the NOFILTER clause at the end of the SQL do for you?

>Mark, I hate to be a pest, but I've been playing with this, and I can't figure out how to make it work.
>
>After creating the cursor using SQL, when I try to issue the CursorSetProp's, I get a bunch of errors saying that they are invalid on table cursors.
>
>Clearly I'm missing something basic here. How should I be issuing the SQL statement? I'm using a normal "Select * from ctracts into cursor v_contracts", and I can't use any of the cursorsetprop()'s against v_contracts.
>
>I know about making cursors updatable using "Use DBF() again in 0", but I don't see how that really helps in this situation.
>
>Any help would be appreciated.
>
>Alan
>
>>The problem you will have at runtime is clashing view creations from multiple users doing this within the common DBC. I still recommend creating a cursor using SQL. You can then make the cursor updatable:
>>
>>CursorSetProp("SendUpdates",.t.)
>>CursorSetProp("Tables","dbcname!mytable")
>>CursorSetProp("KeyFieldList","keyid")
>>CursorSetProp("WhereType",1)
>>CursorSetProp("UpdatableFieldList","keyid, descript")
>>CursorSetProp("UpdateNameList","keyid mytable.keyid, descript mytable.descript")
>>CursorSetProp("Buffering", 5) && optional [my preference]