We are a group of users of Blackbaud products and are not affiliated with Blackbaud. We'd love to have you join our community to help and be helped in getting the most from your Blackbaud software.
Register now to join us to get independant advice on your system, connect with 3rd party consultants to help you maximize your database and have a real alternative to the official Blackbaud website.
Your constituent will not show up in the report because you have limited the date range to a time period when this person did not make a gift greater than 4k and since it is an "AND" statement and not an "OR" statement, nothing exists that would pull this person into your report.
I understand that part... but why do those two relate to each other, but not my other example...
Quote:
Originally Posted by dabatasediva
Your constituent will not show up in the report because you have limited the date range to a time period when this person did not make a gift greater than 4k and since it is an "AND" statement and not an "OR" statement, nothing exists that would pull this person into your report.
It may seem that easy, but you have to think like the computer. It considers your criteria to be one sentence, one complete thought. When you use "AND" as the connector, the system is looking for gifts with a certain date range that are over 4k. The gift in question did not happen during that period, so it doesn't show up.
If you want it to show up on a report, you would have to change the "AND" to "OR". That way it looks at the two pieces of information separately.
In a constituent query, it is basing everything off of the constituent record as a whole.
In a gift query, it is basing it off of the record of the gift.
The computer should think of it as:
Criteria1: Yes or no? If yes, continue... If no, return false.
Criteria2: Yes or no? If yes, continue... If no, return false.
Quote:
Originally Posted by dabatasediva
It may seem that easy, but you have to think like the computer. It considers your criteria to be one sentence, one complete thought. When you use "AND" as the connector, the system is looking for gifts with a certain date range that are over 4k. The gift in question did not happen during that period, so it doesn't show up.
If you want it to show up on a report, you would have to change the "AND" to "OR". That way it looks at the two pieces of information separately.
I questioned this myself a long time ago Mica and when you pull two fields from the gifts section in query the two fields you are querying about are from the same gift.
You can not pull two fields from the gifts section and ask about two different gifts - just not possible. To do that you need to to 2 queries and merge them.
I questioned this myself a long time ago Mica and when you pull two fields from the gifts section in query the two fields you are querying about are from the same gift.
You can not pull two fields from the gifts section and ask about two different gifts - just not possible. To do that you need to to 2 queries and merge them.
That's a matter of opinion. I think that the approach used is quite logical. You're much more likely to want the criteria to apply to the same gift rather than to different gifts even from a constituent query. The only difference between a constituent query and a gift query is the System Record ID that is returned by the query. In one case it is the constituent System Record ID; in the other, it is the gift System Record ID. As long as the fields are from the same "table" they should refer to the same record.
There are some cases where records are stored in the same actual table, but RE interprets them as separate logical tables. The prime case of this is any lookup table. All the values are stored in the same table, but RE treats them as separate.
As Melissa suggested, you can merge queries together to get what you are after. Another possibility is to use two gift summaries. If you count the number of gifts >= $4K and then in a separate summary count the number of gifts between your dates and select where both of them are greater than zero, it will pull in your record.
Drew
__________________ J. Drew Allen
Children's Hospital of Philadelphia
Crystal Reports and SQL Server Consultant
It is better to live your destiny imperfectly than to live an imitation of somebody else's life with perfection.