>We have just started using e-base with our full data installed. We found >an interesting situation running a Overdue Pledge Report. Interesting, indeed. I think you've found a bug. Two gold stars! >Pledges that we have received payments for seemed to have the DAYS OVERDUE >function working fine. When we have a pledge that was made without a >payment received, the DAYS OVERDUE column reports 730596 days overdue not >the true days overdue. The field Days Overdue is a calculated field. If the field Overdue Payment? is "Overdue", the number of days is calculated by [current date] - [date of last payment] -30. So, if no payment has been received, the date of the last payment is blank, and the number days overdue becomes [today plus 30 days]. Note that 730,596 is a bit over 2001.6 years. >Any ideas? Any help? Here's my fix. This assumes that the first payment is due at the time of the pledge and is overdue 30 days after the start date. If your business practice is different, the calculation would involve the payment frequency and the duration of the pledge. Bob or Clif or someone else on the development team, please confirm that I haven't affected something else. Definition of field "Days Overdue" is currently: If(Overdue Payment? = "OVERDUE", Global Date - Last Payment Received - 30,0) but should be: If(Overdue Payment? = "OVERDUE", Global Date - Max(Last Payment Received, Start Date) - 30,0) -- -- Dave Shaw Northwest Classics, Inc. tel: 206-954-7526 fax: 206-625-1338 ------------------ 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 ---------------------------------------------------------------------
