>Hi there.
>
>Over the past while I have tried to understand what triggers my VFP remote views to proclaim that the base tables have changed ...
>
>I know that this is caused by a change to the sql table's structures ... makes sense. When I have had to add a field to the sql table, I have simply been ensuring that I go into any remote views that use the effected table and make sure I have entered the update tab, and then resaved the remote view.
>
>My question is ... when I change a sql table, not all remote views that use the table have this problem. Why?
>
>It seems like the view that I added all of the fields to the remote view using ADD ALL are effected. Remote views that only have some fields are not *always* effected. But this is not always the case.
>
>Does anyone have a clear understanding of this. Or some suggestions as to a better way to handle this if remote views are being used?
>
>Thx, in advance, for any assistance in this regard.
>
>Scott Barker :-D

The best way to avoid getting this error is to reverse the order of a couple of fields in your remote view. What happens is even though you have selected all of the fields in the View Designer, and the the SQL Select statement appears to be "select * from {tablename}", the field mappings are still being recorded for all fields separately in the DBC. By changing the order of a couple of the fields in the select statement you will get around this problem.