dbTalk Databases Forums  

Having a problem finding through filtered multi-match portal

comp.databases.filemaker comp.databases.filemaker


Discuss Having a problem finding through filtered multi-match portal in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
audleman@quasika.net
 
Posts: n/a

Default Having a problem finding through filtered multi-match portal - 08-05-2005 , 02:23 PM






Here's my situation:

I have a table called Contacts that tracks people and is used across
multiple departments.

All communication in the organization is stored in a table called
Contact Log. Contacts match to log entries based on their primary key,
contactID.

Each log entry has a Type, such as 'Note' or 'Donation'.

My problem comes when I try to make a filtered portal to only display
log entries with type 'Donation' and then perform a find through it.

I set up this portal by creating a field in Contacts called
g_DonorMatchKey which is a global text field that contains the value
'Donation'. I created a relationship called 'Donations' which is:

Contacts::contactID = Contact Log::contactID
AND
Contacts::g_DonorMatchKey = Contact Log::Type

I built a portal using this relationship. It works just fine for
viewing. It only shows the donations, of which there are 9,000.
However when I do a find through this portal, it returns 42,000
records, which is all the log entries, donation or not. It appears to
be ignoring the second match criteria of my relationship in performing
this find.

Can somebody help me understand why this find isn't working?

A big thank you,
Kevin


Reply With Quote
  #2  
Old   
Shadenfroh
 
Posts: n/a

Default Re: Having a problem finding through filtered multi-match portal - 08-05-2005 , 03:51 PM






I may be missing the point, but here's what comes to mind.

(Bold) Assumptions
--The "relationship" called Donations is actually a Table Occurrence (TO).
--When you say you are doing a "find through the portal" you are actually
doing a find on a layout that is based on the "Donations" TO

If those assumptions are true: The issue is that a TO contains ALL records
in the base table. The TO itself isn't filtered, unless you're looking at it
from a particular perspective, as when you look at Donations in a Portal on
a layout based on Contacts.

--

Shadenfroh
shadenfroh (AT) yahoo (DOT) com

<audleman (AT) quasika (DOT) net> wrote

Quote:
Here's my situation:

I have a table called Contacts that tracks people and is used across
multiple departments.

All communication in the organization is stored in a table called
Contact Log. Contacts match to log entries based on their primary key,
contactID.

Each log entry has a Type, such as 'Note' or 'Donation'.

My problem comes when I try to make a filtered portal to only display
log entries with type 'Donation' and then perform a find through it.

I set up this portal by creating a field in Contacts called
g_DonorMatchKey which is a global text field that contains the value
'Donation'. I created a relationship called 'Donations' which is:

Contacts::contactID = Contact Log::contactID
AND
Contacts::g_DonorMatchKey = Contact Log::Type

I built a portal using this relationship. It works just fine for
viewing. It only shows the donations, of which there are 9,000.
However when I do a find through this portal, it returns 42,000
records, which is all the log entries, donation or not. It appears to
be ignoring the second match criteria of my relationship in performing
this find.

Can somebody help me understand why this find isn't working?

A big thank you,
Kevin




Reply With Quote
  #3  
Old   
audleman@quasika.net
 
Posts: n/a

Default Re: Having a problem finding through filtered multi-match portal - 08-08-2005 , 12:07 PM



The "relationship" uses the criteria I wrote above to connect the
Contacts table to a table occurrence of the "Contact Log" table called
"Donations".

Your second point is incorrect, I am doing a find through a portal. The
portal is on a layout based on the Contacts table that points to the
"Donations" TO. I find by entering a '*' into the 'Notes' field in the
portal. The found set is actually a list of Contacts that have an entry
in the Contact Log table.

The problem being, of course, that it returns people who have entries
that aren't donations.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.