The relationship is as you say CONTACT A::Dept = CONTACT B::Dept. On
the layout I have a field "Department" that is a drop down list. That
when a department is selected the contact names for only that
department appear in a portal. When I highlight a contact to update
information then select another department via the drop down list
that contact' department changes to the one selected.I have used this
relationship and the conditional value list before and never had this
problem. I assume it is because of the self-joined relationship.
Peter
On Feb 22, 2008, at 5:25 PM, Tom Elliott wrote:
Peter
It sounds like your relationship is: CONTACT A::Dept = CONTACT
B::Dept and that in order to "go from one department to the next"
you are actually changing the Dept field in the current CONTACT A
record
If I've got that wrong then perhaps you could post more details:
what the relationships is, exactly how the value lists are defined
and used, what you've got on your layout (that's relevant to the
relationship) and how you are "going from one department to the next"
cheers
Tom
On 22 Feb 2008, at 20:49, Peter Kilcoyne wrote:
Hi Folks:
I am designing a contact database in FMP8.5 and I have created a
self-relationship between CONTACT A and CONTACT B. I have a
conditional value list for the contact names that is based on
their department. When I go from one department to the next the
contact name that was in the previous department falls under the
department that I just moved to.
What is happening is that the department name for that contact is
changed to the department that I went to. In the relationship set
up box creating new records is not on for either CONTACT A or B.
The value list for departments is based on CONTACT A and the one
for contact name is based on CONTACT B.
Can anyone tell why the department name would be changed simply by
selecting another department o view?
TIA,
Peter