I have run into some VFP behavior that I don't quite understand. Here is some background:

I have taken it for granted that when defining a view in code with CREATE SQL VIEW, VFP does a certain amount of work for itself like: setting the datatype property for each field, setting the UpdateName for each field and resorting to a default WHERE type for the view. I have come to rely on this.

But every once in a while, after I create a view in code, VFP does not set the UpdateName property for all fields. Some fields will have a blank updatename property, and some fields will have the name of the field, but with no table (No, these are not calculated fields). This appears to happen even occasionally with simple, single table views. I have tried to track down what might be different about these fields that confounds VFP so, and have come up empty handed. The interesting thing is, if I open the view in the view designer, change something and save, the properties are filled in correctly. But this solution won't work, as we all know, because not all views can be opened in the view designer.

Does anybody have any insight?