>Initially, the StatLi table was prefixed with APPDATA! - eView assumed, I assume <s>, that StatLi was part of my Appdata.dbc, the DBC that houses the view definition.

EView didn't assume anything. VFP did when you created the view. The values you see in the fields list are those that are generated when the view is created.

> I delete the "APPDATA!" string and I then added the two other free tables involved in the view, so, there is now three free tables in the tables property, comma delimited.
>

You should limit the tables in the Tables property to only those that are being updated. And generally, updating more than one table from a view is a bad idea. What happens when you delete a record? Add a record? Unless you have some very unusual data structures, you probably don't want to do that.


>I have no conventional views whatsoever. They all involve 2.6 and/or VFP free tables. The system is basically a massive 2.6 legacy system that is being written over to VFP. The VFP system operates concurrently with a 2.6 interface on the same data.
>
>Any thoughts?

Well, it's impossible for me to debug if I can't reproduce it. I would be interested to see if you have that problem on other views (even if you have to conjure one up. :-))