Calculated Field on Form needed on Report

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a report that list the balancedue. The balancedue is calculated from
the total due - paymentstotals on the main form. After a payment is posted,
a receipt is printed and if a balancedue exist, the balancedue letter is
generated.

How do I go about getting the balancedue without referencing the form. FYI,
I did have the report referencing the balancedue on the form and it cause
lot's of problems.

Considering that the balancedue is a calculated field, should I calculate
the balance and save it to the table?

Thanks,

Ray.
 
Ray said:
I have a report that list the balancedue. The balancedue is calculated from
the total due - paymentstotals on the main form. After a payment is posted,
a receipt is printed and if a balancedue exist, the balancedue letter is
generated.

How do I go about getting the balancedue without referencing the form. FYI,
I did have the report referencing the balancedue on the form and it cause
lot's of problems.

Considering that the balancedue is a calculated field, should I calculate
the balance and save it to the table?
Click to expand...


You could recalculate the balance due in the report.

OTOH, using the value from the form is ok as long as the
form is open and the value has been calculated before the
report is opened. What kind of problems did you have with
this approach.
 
Marshall,

The problem that I was having is the "looping" that I was describing
yesterday in another post on the forms/coding board. (Looping might not be
the best word to use, however, that what it appears to be doing when looking
at it on the screen)

I finally narrowed the problem down to this individual report and then
ultimately the one field (on the report) that referenced a calculated field
 
That problem! Oh my, that is a nasty situation. You must
have done some serious debugging to pin that thing down.
Good work. (Don't ask me to explain why/how it happens to
exhibit that symptom)

You should(?) be able to perform the same calculation in the
report, which is not a bad thing if it's relatively simple.
If it has any degree of complexity, you may want to
encapsulate the logic in a standard module function that you
can use form both the form and report/
 
Back
Top