>First of all, it is not recommended to have updateable view if based on more than one table. At least it is tricky if possible to handle updates in this case.

As I said, I have little database experience but reading the VFP documentation, which shows examples of views using two or more tables, I thought that this may be the way to go. If the view from developers is that it is inadvisable, then I will certainly take that advice. From yours & Hilmar's advice, I am thinking of using forms & writing my own SQL.

>
>From your #1 below, I do not get it, how may result contain the same number of records as table1. Is there only one-to-one relations?

Yes, each part will only be of one type, in one location & data will be on one CD. But in the opposite direction, there will be more that one part of a particular type, a location may store different parts & data for multiple parts may be on a single CD. These rules determined the tables I created - as long as the tables are correctly populated, there will always be a matching number of records in the result to that in table 1.

Again, thanks for your time
Irene