Steve,
Its kind of hard to explain but as an example you have a list of
invoices to be paid and an amount of say $5,000 was received which was
less than the total of the 20 outstanding invoices.
As you draw down the $5,000 paying off each invoice (starting from the
oldest date) a calc field is needed to maintain the balance of the
amount left that can be used to pay the following invoices. If you used
a straight calc field it would not be correct, as each invoice was
removed it would recalculate that field and be 'ahead' of itself in a
looping script by reducing the amount left to be available before that
invoice was paid.
As I said its hard to explain but I've removed the global field and its
working fine. I have 3 other clients using the original script and they
haven't had any problem, its just been this one client who has found
this anomaly.
Lee Mills
Steve Cassidy wrote:
Lee
Somehow I'm not following your need for a global calculated field.
If you are looping through records and performing some process at each
record, then the calculation (of payment-amount-due) should surely be
based on that record? A regular calc field would do.
I don't know what the problem is with your global calc, but I can
imagine update problems as you move from record to record, depending
on when the context changes from one record to the next and when data
is committed.
Are you sure you need a global here?
Steve
On 10 Sep 2008, at 12:13, Lee wrote:
Forbes,
The global field was set in the Defined Fields as a calc, not using
SetField is that a problem ?
Lee Mills
--
