Could it be that you have a rule in your DBC that doesn't permit orphan records?

--------------------

>>>I have a VFP 6.0 app written for a school. Classes are divided into Levels, Sections, and Activities. Levels and
>>>Activities are assigned student by student. Sections can then be assigned programmatically to all students
>>>who have received Level-Activity designations. The process is fairly complicated and works pretty well.
>>>EXCEPT: When the smoke clears, those students who do not have Level designations are marked for
>>>deletion. Nowhere in any of the code does the word DELETE appear. The placement code operates on
>>>local, updatable views for the most part.
>>>
>>>What else causes a record to be marked for deletion besides DELETE?? I have absolutely no idea
>>>where to even look for this one . . . .
>>>
>>>TIA,
>>>John
>>
>>

---

Grids with deletemark = .t. (Default) ? SQL delete than insert in update method ?
>>Cetin
>
>Delete trigger?
>Record level rule?