Ok, FMPro/ebase users ...

If I want to find all the people who have addresses in Denver or Boulder in
ebase, I start a FIND, put Denver in the city field, create a new request,
and put Boulder in the city field.  When I click FIND, they all come up just
fine.  In this case, the requests are related by the logical operator
'OR' -- that is, anyone who lives in Denver OR Boulder will be in the found
set.  Pseudo-code for these criteria in a query some typical database might
look like:

city="Denver" OR city="Boulder"

(no, this isn't FMPro scripting ... just a visual way for me to understand
the query)

HOWEVER,

If I want to find all of the people in Denver who don't live in zip 80202, I
do two requests again.  Namely, I start a FIND, put Denver in the city
field, get a new request, put 80202 in the zip field, click OMIT, and
execute the query by clicking FIND.  Pseudo-code for these criteria might
look like:

city="Denver" AND zip<>"80202"

In this case, the two requests are related by the logical operator 'AND' ...

Does anyone else find this aspect of FMPro a little confusing?  When do
multiple requests relate to one another by AND, and when do they relate to
one another by OR??  Is it solely a matter of whether OMIT is checked?

(Here's wishing FMPro could speak the more standardized Structured Query
Language [SQL] common to so many other database packages ...)

-- Eric Johnson
   Colorado Environmental Coalition


---------------
Eric S. Johnson
Colorado Environmental Coalition
1536 Wynkoop #5C
Denver, CO  80202
303-534-7066

VISIT CEC ON THE www AT http://www.ourcolorado.org


------------------ 
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support  and enter the email address 
you used to subscribe to the ebase support list:: [email protected]

To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
 ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------

Reply via email to