Peter
On 25 Feb 2008, at 13:56, Peter Kilcoyne wrote:
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.
Let's be clear here: the field used on the left side of the
relationship ("CONTACT A::Dept") is the same as the layout field
("Department") formatted as a dropdown, yes?
If not then:
... when a department is selected the contact names for only that
department appear in a portal.
doesn't make sense
But, if 'yes', when you
... select another department via the drop down list
you are actually changing the *data* for the current record in
CONTACT A - so of course
that contact' department changes to the one selected.
To put it another way: by virtue of your relationship, your portal
*always* shows contacts in the same department as the current
contact; changing the current record's department will change the
contacts in the portal to those in the 'new' department and that is
the *only* way to view contacts from another department in the portal.
Do you want the portal to:
a) show contacts in the same department as the current contact (which
is what you've done)
or
b) show contacts from any (specified) department?
It seems you are somehow hoping to combine both the above, but this
is not really an option because in a) the portal reflects (something
about) the current record's data - changing the data changes the
portal, whereas in b) the portal is simply a device for showing some
data that may or may not be related to the current record
Therefore I'd say you need to decide which of the above you want and
if b) then I suggest you need a separate global field (gDepartment)
which is used on the left side of the relationship and put on your
layout formatted as a dropdown. Note however that as you move from
record to record in CONTACT A, gDepartment will remain unchanged and
the portal will therefore not automatically 'update' to show contacts
in the same department as the current record.
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.
I'm still unclear what part, if any, the value list of CONTACT B
names plays in this.
I don't believe the fact that this is a self-join is particularly
relevant to your problem
cheers
Tom
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