>I constantly run into a problem when adding fields to an existing table. Create a local view based on a table in the DBC. Make all of the fields in the view updatable, including the primary key.
>
>Then go back and add a field to the original table. The view is no longer usable, unless you modify it, and then the system tells you that the table and the view do not match, and resets the update flag on all of the fields back to not update. If you have even one field in the view that is not marked to update, then this does not happen. What should I be doing differently?
>
>Thanks
>Bill

Nothing :), except checking the depending views before changing the table.
This is the default VFP behaviour. The view will complain after adding field to the table if you included ALL fields into the view. (SELECT * FROM... in View SQL option) It does not depend on were fields checked for update or not. If you included only some fields in the view (or even all fields, but one by one, so they are listed like: SELECT myTable.Field1, myTable.Field2,... FROM... in View SQL option), adding of the new field will not cause this, whether they were checked for update or not. Of course, if you change the name of the field included in the view, the view will complain and remove all selected fields from the Field an Select Criteria tabs. It is not a bad idea to periodically use GENDBC utility from VFP to be able to re-generate your database at any moment. Or use Stonefield Database Toolkit.

HTH,
Nick