Hi Erik,

I am having the same problem. In my framework, grids ar built using a builder that automatically creates the proper pview as RecordSource. First the view is created in the program and then the view designer is opened for the user to check that there are no mistakes. Lately I am having problems at 2 sites, and, what is worse, I can never reproduce the behaviour exactly. However, also this crazy thing happened to me:
In one particular view a column, called RAGCLI, kept popping up. This column had existed before, but had also been deleted some weeks ago. So, using Steve Arnott GenDBCx, I recereated the database from scratch, making sure that RAGCLI didn't exist in the generated source. (It was not there). I then generated the pview through the builder and RAGCLI was there again.
So I recreated the dbc again from scratch, generated the view from the command window, bypassing the builder, and put the whole database through a new copy of StoneField (I mean empty cdbkmeta & sdtmeta), launched the validation and RAGCLI was there again. SDT was able to continue but my confidence in the whole process was a bit shaken. References to RAGCLI were in the dictionary.
I then looked for old copies of the offending table in all my machines, at home and in the office, without finding it anywhere.
If it may be of some help to trace the problem, I created an empty database again and added just the table and the view: no problems there.
Of course, I've tried reindexing, packing and validating the dbc, all to no avail.

Silvio

>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?