Erik:

>Is the updatable field from the same table?

Yes.

There is also a join on another table that has a PK defined and an updatable field.

So, both PK's are not updatable but there is one other field from the two tables with pseudo-PK's specified that are defined as updatable.

>Are there any other tables listed in the Tables property on the Advanced properties page?

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

I would point out that despite the issues raised, the view appears to work. It updates two tables out of the three involved in the view. Both have "candidate" keys specified as primary KEYs (so far as eView is concerned).

>I haven't seen this, and you're the first to report it- but then again, I have never used EView on a view that uses free tables. Do you get this with more conventional views?

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?