Eric,
As I recall this problem, it is simply one of the SUM:YTD$ field (in the
Names file), which is a calculated field, not being evaluated when the
field that it uses to calculate it's value is empty. You can go to
Define->Fields->SUM:YTD$->Options and uncheck the box that says "Do not
evaluate if all referenced fields are empty. There may be other SUM:
fields that do the same thing, so you can make the same change on those
fields.
The Replace All Find Fields script and the Replace Current Find Fields
scripts in the original ebase returned different values for YTD - $0 in
the case of the "Replace Current" script and blank in the case of the
"Replace All" script. Since the "Replace Current" script is called when
you run the Home script (e.g. by clicking the Home button from anywhere
in ebase), it returns the $0 value. But when you run the Replace All
script, all records without payments for the year get a blank field.
This can cause odd find results if you are looking for records with a
zero dollar amount for the year. That's why I made this change.
I still haven't figured out why the two scripts end up with different
results, but they seem to calculate the result using different
intermediate (holder) fields. Why this is done this way is a mystery to
me. Jack?????
Carl
Eric Johnson wrote:
>
> Dear ebase listers,
>
> I'd written a couple of times in the past about the YTD$ / Last Year$
> calculations as they show up on the HOME screen in version .102. The bug is
> known, I'd just had trouble fixing it the first time through. Now the #s
> seem to be okay.
>
> Now, though, I notice that the YTD $ on the HOME screen is blank for some
> records, and not for others. Running the script 'HOME' for any given name
> record fixes the problem, putting a "0.00" in that field. Actually, it's
> probably the running of 'Replace Current Find Fields' that does it, but
> 'HOME' runs that as a sub-script.
>
> Anyhow, annoyed by the blanks on the screen, I developed the following
> script to fix it. I'm not much of a FileMaker scripter, but this made sense
> to me and seems to work. Does anyone see any reason NOT to use it on a live
> copy of the database (it's just been tested on a copy to this point)?
>
> Here's the script:
>
> Loop
> Perform Script [Sub-scripts,"HOME"]
> Go to Record/Request/Page [Exit after last, Next]
> Exit Loop If ["RECORD NUMBER>2360"]
> End Loop
>
> (there are 2361 names records in the database -- I did a find all, went to
> the first record, and ran the script)
>
> TIA for any comments you may have.
>
> Cheers,
>
> Eric Johnson
> Colorado Environmental Coalition
>
> ------------------
> 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
> ---------------------------------------------------------------------
--
Carl Paulsen
New Hampshire Rivers Council
54 Portsmouth Street
Concord, NH 03301
603-228-6472
603-228-0423 Fax
[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
---------------------------------------------------------------------
