Carl, I finally got to this "phase." Knowing that you had at one time
offered to come and do this, I thought the experience would be
useful, so I set to . . .
The first few seemed to go OK and then I encountered some problems.
My question is, does it much matter if I go ahead and make some other
modifications in the meantime -- meaning until you can come help if
you think it necessary?
As you probably remember, I'm already using FM Pro 5.5 and have, I
think correctly, updated 1.02 to run with it.
>5) Fixed bug in the way Global Date is formatted in PLEDGES
>------------------------------------------------------------
>TO ADD THIS FIX TO YOUR VERSION OF EBASE:
>--------------------------------------------
>A) Determine if this is a problem:
>
>-Get into ebase using your master password. Once you're on the HOME
>screen, Click on the Pledges button
>and them the View pledges button to bring you to the pledges_.102 file.�
>Now select: File->Define->Fields.
>
>-Double-click on the field named " Global Date".
>
>-The "Specify Calculation" dialog box will appear.
I have no pledges but went to the pledges file anyway. What appeared
is an Option Box. The field is described as Type: Global and Option:
Date. I can't get to the specify calculation screen
>The correct
>calculation
>for this field is as follows:
>
>CONSTANT::gToday
>
>-And that the Calculation result is field on the Specify Calculation
>dialog box is set to "Date"
>
>PROBLEMS WITH SLOWDOWNS IN TRANSISTION FROM PAYMENT HISTORY TO PAYMENT
>-----------------------------------------------------------------------
>
>6) Fixed bug causing slowdown in transition from payment history to
>payment with large data sets
>
>TO ADD THIS FIX TO YOUR VERSION OF EBASE:
>-----------------------------------------
>A) You should determine if you have this problem.
>
>-Get into ebase using your master password. Once you're on the HOME
>screen, select: Scripts > Scriptmaker
>
>-From the Define Scripts for Names.102 dialog Double click on the Script
>names "View Payments Script"
I find this but the name does not include the word "script."
>
>-In the Script Definition for View Payments dialog the correct fourth
>line
>from the top should read:
>If[not IsValid(All Payments All Names::Record Number)]
I see the following
If["not IsValid(All Payments All Names::Record Number)"]
When I copy and paste the "correct" line, it still shows on screen
with the quotes.
>BUG IN EXPIRATION OF INDEFINITE MEMBERSHIPS
>---------------------------------------------
As of now, I have no pledges and no "indefinite memberrships.
>
>8) Problem with expiration of indefinite memberships
>--------------------------------------------------------------------------
>Fixed Bug where ebase, under some conditions, erroneously reported the
>expiration of indefinite memberships as the last expiration date of a
>past
>full membership for that member. eBase now figures a changing future
>date
>for expiration of indefinite members based on system date.
>-Double-click on the field named "Expire Date".
>
>-The "Specify Calculation" dialog box will appear. The correct
>calculation for this field is as follows:
>
>Case(
> Payment For <> "Dues", TextToDate(""),
> IsEmpty(Start Date),TextToDate(""),
> Duration = "Indefinite", Names::gToday+730,
> Min(
> Date(
> Month(Start Date) +
>If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0),
> Day(Start Date),
> Year(Start Date) +
> ���
>If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0)),
> Date(
> Month(Start Date) + 1 +
> If(PatternCount(Duration,"M"),TextToNum(LeftWords(Duration,1)),0),
> 1,
> Year(Start Date) +
> If(PatternCount(Duration,"Y"),TextToNum(LeftWords(Duration,1)),0))
>-
>When I attempt to past this script and click on OK, it highlights
>"Payment For" in the script and says this field can not be found.
So it will not accept the change.
>NEW FEATURE: DATA RECOVERY AND EXPORT UTILITY
>----------------------------------------------
>9) Added script to assist in data recovery/exporting to new ebase�
>clones
>--------------------------------------------------------------------------
>
Carl, I have a feeling this is important but it surely looks
daunting. I can't imagine a situation however in which I'll be using
ebase clones so maybe it's unimportant. Advice?
Just FYI, you sent me the bug fix file on 3/18/02.
--
Simply,
John
mailto:[EMAIL PROTECTED]
http://simsoc.org
Thank you for you!
------------------
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
---------------------------------------------------------------------
