Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Reports / Printing / December 2005

Tip: Looking for answers? Try searching our database.

Calculated Field on Form needed on Report

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ray Todd - 02 Dec 2005 21:20 GMT
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.
Marshall Barton - 02 Dec 2005 22:34 GMT
>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,
[quoted text clipped - 7 lines]
>Considering that the balancedue is a calculated field, should I calculate
>the balance and save it to the table?  

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.

Signature

Marsh
MVP [MS Access]

Ray Todd - 03 Dec 2005 00:32 GMT
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
on the open form.

> 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 Barton - 03 Dec 2005 07:29 GMT
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/
Signature

Marsh
MVP [MS Access]

>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
[quoted text clipped - 11 lines]
>> report is opened.  What kind of problems did you have with
>> this approach.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.