Mark,
What does the insert trigger do? It may do some checks on the PK value and if it doesn't adhere to its rules, it returns .F..

When you added a new record directly to the table, did you use APPEND BLANK or INSERT INTO. If the former, the trigger may return .F. because the PK field can't be blank.

>I am doing maintenance enhancements to an app developed in VFP 5. The lookup tables never had utility data-entry forms made for them so the users couldn't add more values to their lookup tables.
>
>In this app, the DBC has made extensive use of stored procedures and triggers. The RI Builder reveals that table updates are allowed for entering new lookup values but will not allow deleting any existing ones that might create orphans (of course).
>
>However, when I try to append a new record directly to the table a trigger fires and says I may not violate the integrity of the table. Same thing happens while testing a data entry form that I created with the table added to form's Data Environment(DE). Also, I tried using a view of the table and added it to DE of form in place of the table, but same error msg came up. I even created a form using Form Wizard based on this table, and it would not let me add a new record to the table. Yikes! Does anyone know what I may be overlooking here?
>
>Thanks,
>Mark