If anyone is interested in one example of how to do this, I just customized 
a version of Ebase V1.0.3 to track this type of data and I'm happy to share 
the solution reached in this case.  It seems to be working pretty nicely at 
this point.

The customization went as follows:

1. The "original donor" and the "proxy donor" (the last entity to touch the 
money before it arrived) have records in NAMES.

2. The PAYMENTS database has the following field additions:

     a. "proxy_donor_record_number"

     b. "c_proxy_donor_name" - calculated field holding some kind of 
description lifted
         from the NAMES record with a RECORD NUMBER that corresponds to the
          value entered in "proxy_donor_record_number.

     c. "original_donor_record_number"

     d. "c_original_donor_name" - calculated field holding some kind of 
description
          lifted from the NAMES record with a RECORD NUMBER that corresponds
          to the value entered in "original_donor_record_number.

3. The PAYMENTS database also has two new relationships:

     a. one that matches values of the "proxy_donor_record_number" to 
values of the
         NAMES database RECORD NUMBER field

     b. one that matches values of the "original_donor_record_number" to 
values of the
         NAMES database RECORD NUMBER field

4. I then added a new layout to the PAYMENTS file which assists the user in 
searching for and entering a record number for a specific NAMES record into 
the "proxy_donor_record_number" or "original_donor_record_number" field.

5. The Ebase "payment entry" layout is modified slightly:

     a. I've displayed the new fields noted in point 1 above.

     b. I've added the following buttons:
          i. one that opens the new "search for a NAMES record" layout
          ii. one that writes the RECORD NUMBER value returns by a NAMES
              search into the "original_donor_record_number" field
          iii. one that writes the RECORD NUMBER value returns by a NAMES
               search into the "original_donor_record_number" field

During use, the database worker will fill in two payment records whenever a 
"proxy donation" is received:

     * one recording a payment for the "original donor" and indicating who 
the "proxy donor"
         was by entering a value in the "proxy_donor_record_number" field

     * one recording a payment for the "proxy donor" and indicating who the 
"original donor"
          was by entereing a value in the "original_donor_record_number" 
field.

You can choose to enter zero or nonzero values on each of these two payment 
records, depending on the concerns you have about tracking the 
contributions, double-counting contributions, etc.

**************************************************************
Larry F. Bednar
Consulting in Statistics, Quality, Data Management
Portland, OR  503.493.8542   [EMAIL PROTECTED]
**************************************************************


------------------ 
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