>Hi Bret ---
>
>Sorry you're having so many problems with this :-) Maybe you're going to have to think about doing a single row TABLEUPDATE() along with the flag manipulation when a row is deleted/recalled.
>
>>
>>OK Ingnore the previous message about duplicate record, I found that I did not check the right box for 'SQL Where clause includes' I chose the key fields only option and this fixed the 2 record problem, but it did not fix the fact that the record in the local table is still deleted, even though I recalled it before the tableupdate was done. The data was changed, but the fact that the record is still deleted is the main concern now.

I have discussed this topic at length with my fellow programmers and are deciding on a strategy for updateable views. I think we are leaning toward this:
The user can delete anything they want, but if they press save (tableupdate) the deleted record is deleted and they will never see them again. Because we will surround our requery() with a set deleted on then set deleted off. I was worried about if the user deleted a record and saved then came back later and readded the same record (the keys to the table will be the same as it is a many to many relationship). I figured FoxPro would not like having another record in the table with the same keys as the one that was deleted, but to my great pleasure, FoxPro just replaced the deleted entry with the new non deleted entry if the user readded a record that was previously deleted.