Thanks Mark, certainly sql cursors bring down data a whole lot faster than does requerying a view. Truth is I've never really considered using a cursor and making it updatable.

This is an idea worth considering.

Again, thanks.

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]