Allan,

>1. Is my thinking correct on duplicate field names? If not, what is the correct syntax for the SQL statement?
>2. If the common field is changed, are both tables updated with the change?

No, If you want both fields updated they both need to be in the SELECT. Either one or both can use aliases to avoid the _a _b problems you described.


>3. Are all tables, when combined in a primary business object by an SQL statement in one view updated successfully if the field “DBSETPROP” lines in “VIEWS.PRG” define update .T.?

The problem you may have is with primary keys. In a MM view, one primary key if fetched from the database, the other would need to be added programmatically. I tried this once and finally just separated the combined view into two single views with the business objects related to each other.

I still use combined view sometime, but only one table is updatable, the others are used for lookup purposes or retrieving related data for viewing purposes.

>
>Thanks Allan Godney.

HTH

Rex