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

OK.

>You should limit the tables in the Tables property to only those that are being updated.

Now I know. Thanks.

>And generally, updating more than one table from a view is a bad idea. What happens when you delete a record?

This particular view is in a form that has no Add/Delete option. It is a batch update process. However, I take on board your concerns.

>Well, it's impossible for me to debug if I can't reproduce it.

I am surprised no-one else is using eView with free tables. I would have thought that free tables were prime candidates for use in views in view of legacy system issues.

>I would be interested to see if you have that problem on other views (even if you have to conjure one up. :-))

OK - I will let you know.

Thanks for replying and thanks for the tool, Erik.