Svein Erling.

> > Unfortunately, the results stay the same.
> >
> > Playing around a bit with different view approaches and types of
> > joins, it seems the OUTER join is the problem.
> >
> > If I either create the view with the last join as "join" and
> > not "left outer join", the view works as expected.
>
> Didn't you just say that the results stayed the same with the above
> changes? If so, the last outer join was replaced by an inner join.

When I checked for field uniqueness, I did not change the joins. What
I meant by the "the results stay the same" remark, was that the
joined field kept being null AND not null, regardless of the field
name (alias).

In the production database inner and outer joins do not make a
difference, because at the present state the outer join will always
find data - and no rows are excluded. There will, however, be times
on the production system where empids are not present for some mgrs.
v_a should still list all rows.

Semp