>Let me toss this out as a possible solution to a problem I've got.
>
>I have fields in tables that are keywords. The fields have been around for years, but the problem has only just surfaced because apparently TableUpdate() generates an UPDATE command that is invalid due to the presence of keywords.
>
>It is not really an option to rename the fields, because there are many other external apps that count on the field names being such.
>
>My solution is to create a field in the table that mirrors the value of the problem field. I will use triggers to keep them sync'd up. I'll only make the new field updatable in the views, so TableUpdate() should not have a problem. The external code can reference the old field.
>
>Any thoughts?
>
>Bob

For most functions, you can usually get around the problem by explicitly using the field name with the table name -- mytable.fieldname or mydb!mytable.fieldname

Jim's suggestion is good, too, but I have not tried to utilize *KEYFIELD AS "NEWFIELD"* in a view. As long as VFP knows which field in the originating table it goes to then it would work.