# 4120 Loading a Replication Updates File into a Table with Computed Columns Can Cause Load Error

---

Loading an update fails referencing a table field that does not exist in the source or target databases and that is not in the RowData of the update.

Based on the contents of the error message, I surmised that the problem was caused by there being a computed field in the table being updated. When I alter the table so that the field is no longer computed, the update loads without error.

I have included the source catalogue as well as the target catalogue along with two updates that show the issue. The field of interest is Payment.CardType and the error when loading states that the field "Visa" for the first example and "MasterCard" for the second example, does not exist in the table Payment.