This last weekend I just finished upgrading our v1.02 ebase runtime to
v1.03 with full Filemaker Pro. Once we got this accomplished everything
looked good. We checked payments, pledges, gerenal reports etc.

Today we found that four pledges were entered previously with the wrong
amount and duration. Here is what we did:

-We found the name
-Accessed the pledge screen for the pledge (which was closed - fully paid)
-Changed the total amount of the pledge from $240 to $360
-Then we changed the months from 2 months to 3 months duration
-Then we added the final payment of $120
-Then we went back into the pledge screen to open the new pledge for the
coming year.

It was at this point that things went down hill. When opened the new
pledge screen, immediately there were payments attached even before we
entered the new pledge information. These payments were actually from
another name. When we completed the new pledged and then accessed the
payment screen the payment showed up as a different name but the pledge
payments were attached both to the currect member and this other member
with the new pledge.

I tried this on using the runtime version of V1.03 and it did the same
thing. The only inconsistance was it didn't aways grab the same person's
payments.

We then went back to our backup of version 1.02 and did the same process
with no problem at all.

So what do you think. Is this a V1.03 bug, or is this a botched attempt
and upgrading from 1.02 to 1.03?

David Rodgers
Institute for Individual and World Peace

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