>Hi Aleksey,
>I certainly missed the part in the VFP docs saying that RECALL does not work with views - can you point me to that part of the docs?
>On the other hand, if RECALL is not a SQL command, shouldn't it be disabled, or generate an error when used with a view?
>Thanks.
>
Hi Doru,

Well, RECALL does work with view and there is no reason to disable it.
Modifying view cursor and modifying base table are two different operations, think about that.
VFP help is not perfect, but, after reading help about view properties, anyone will understand that SQL commands are used to update a base table. After all, if it is still not clear how it works, try it out before relying on some assumptions.

Doru, please be reasonable, current behavior is not a BUG and it is not going to be changed.

Thanks,
Aleksey.

>>>I was getting duplicate keys in an app using an updateable local view to update a free table. Yesterday I discovered that recalling a deleted record in a view DOES NOT RECALL the record in the base table, but actually creates a new record, a duplicate!!!
>>>
>>>Unless I missed something, this makes updateable views not only useless, but extremely dangerous.
>>>
>>
>>Hi Dory,
>>
>>You missed a very important detail - local/remote view is a SQL VIEW. RECALL is not a SQL command. In VFP, SQL view modifies a base table using SQL-DELETE, SQL-UPDATE, SQL-INSERT, none of those commands recalls deleted records.
>
>>
>>Thanks,
>>Aleksey.