Robert,

You probably need to use the UpdateName option of CursorSetProp or DBSetProp to "translate" the remaned field back to the original field name. Hopefully TableUpdate will not get upset when you do it that way, but I guess you will have to try it to find out.

Good luck,

Jim N

>Maybe 'm doing something wrong, but when I use the "AS", the changes are not propogated to the base field. It's like VFP thinks it is a calculated field, and does not know it is really just a rename of a field.
>
>I agree with the "mytable.fieldname" solution. Unfortunately, I'm trying to use TABLEUPDATE(). I think it generates SQL updates like "UPDATE product SET desc = 'XXX'", instead of "UPDATE product SET product.desc = 'XXX'".
>
>I've tried to combine the two solutions by naming a field desc AS "product.desc", hoping this would cause the correct UPDATE syntax to be generated by TABLEUPDATE(), but no luck here either.
>
>
>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.