Following up what Erik posted, I have seen this message when there is an outer join with a lookup table and the first row in the result set has a .NULL. value. Foxpro assigns the column a width of one. If you requery the view and the first record now doesn't have a null for the field value, you will get this message. To avoid this, use the NVL( {lookup field}, space(35) ) function. Note that you must use a specific number as the argument to the space funciton--len( {lookup field} ) will return a 1 if the first record in the result set is a null!

>Dear Foxpro Fans,
>
>Occasionally after updating a view I will get this curious error stating to me that the "View Definition Has Changed" when I try to REQUERY the view. This is sort of odd in that all I am doing is updating the data in the view/tables. As I trap the definition change using GetNextModified, I normally will detect the view change and can TableRevert(.T.) to get it back. On this particular occasion not only does it not detect the view change, but when I do an outright TableRevert it does not restore the view definition. All I can do is close the view and reopen it. But this causes other problems. My question is this: Why do I get a view definition change when I am updating data? The error indicates some sort of structural change to the view and nothing to do with the data. But I am not chnaging the view definition.
>
>Curiouser and Curiouser,
>Mike