I am developing a VFP8 application with a colleague and sometimes I need to add new fields to a table, but my colleague may not insert the field in the same position on his version. I wouldn't have thought this matters, but when we run a local view defined as SELECT * FROM MyTable WHERE ?myfilter (from the same database container), I have discovered that unless the underlying table-structure is the same as when the view was originally created, the resulting data appears in the wrong controls (whether in a grid or individual controls on a form).

I know that if a grid.recordsource is refreshed other than using REQUERY() then column.controlsource values are 'lost' and data displays in physical field order, but in this case the view is loaded using REQUERY('MyView').

Short of ensuring our field-orders are in sync. all the time, is there any other way to ensure the correct data appears in the correct controls? I want to keep this view simple using SELECT * - I don't want to specify fields (there are too many!).

I guess hard-coding the SQL command will work for the read-only views, but some views are updatable, in which case it much easier to set-up update properties for many fields in the database container.

Any help would be appreciated.

Alan