No.  Crystal Reports does not allow summary information in the row or column headers. The place to take care of this is your export.  Instead of having one field with all three values, you need to have three fields restricted to one of each of the three values. Drew

I wouldn't expect the number of constituents to change.  I think that you saw gift dates outside of the range you specified and assumed that they were pulled because of the criteria, when what was actually happening was that the constituent met the criteria, because of a smaller sample of gifts, but the output contained ALL gifts.  I ...

QUERY IS NOT A REPORTING TOOL! [quote user="Fred Longhenry"]It's pulling gifts[/quote]  No!  It's pulling CONSTITUENTS and displaying their entire giving history. Query is a grouping tool, not a reporting tool.  If you want to limit the gifts displayed, use export with your query. Also note that the first part ...

There are basically two options. 1)  Create a group on the prospect and put the prospect info in the group header/footer and the solicitor info in the details section. 2)  Use a sub-report.  You may still need to use (1) if you have other one-to-many relationships in your main report. Drew

Are the categories the same field on different rows or different fields on the same row?  I'm assuming same field/different rows, since that's the one most likely to cause problems. Try creating a group on the constituent and then a group on the category making the order "specified order" and specify B, C, then A.  ...

Crystal Crosstab rows and columns cannot be based on a summary.  Your rows are based on a summary (total amount given).  Instead of outputting every single gift in your export, use the gift summary fields and then base your rows on those fields. Drew

It sounds like you are using query for your report, but query is not a reporting tool.  You need to be using export for your report.  The Last Gift fields in query and export behave differently.  What you want can only be done through export. Drew

In order for this to be effective, it would need to run automatically every time a record was changed.  Plug-ins do not run automatically. You could set up VBA scripts to run whenever a record was changed, assuming that you have the VBA module. Drew

The Blackbaud Management Console has a utility to manage the deploy package.  I would recommend using that rather than manually editting the registry. The reason that simply changing the ODBC doesn't work is that the first thing that RE does is look for the deploy directory (based on the registry setting) and compare the deploy settings ...

The easiest way is to create a group on the primary class year, and then add a summary of the Constituent ID using a distinct count. Drew