Hi John, thanks for being willing to help me over this hump.
I thought that was the idea of views, but I'm stuck.

I tried a local view, it looks like this:

SELECT Campunit.*, Facility.fname;
FROM eh!campunit INNER JOIN eh!facility ;
ON Campunit.facilityno = Facility.facilityno;
ORDER BY Facility.fname

I have the View in the DE

When I run the form, I encounter two problems:

"Edits to one of more view may not be permenant, check View's Send SQL updates box"
(and it looks to me like I've got that box checked)

maybe not having this first part right is causing my second problem,

When I click the Next, Next wizbuttons, the Facility name (from parent table) changes, but not the child fields.

Can you suggest what I've overlooked?

Thanks and thanks again
Sylvia

PS- and this is somewhat health-related. Camp health. Env. Health

>Actually, I do this all the time. All you need to do is create a view with the child information linked to the parent table and select the field you want to display (and obviously also all the fields you need in the child table). Then base the form on the view, the data from the parent table is now included in the view because they are linked by the SQL, so you don't have to monkey around with the wizzard form code at all, it automatically updates. Also this way when the client caomes back and says "Oh we need this field too", you only need to include the field in the SQL, and add it to the form.
>
>Try it you'll like it.
>
>John