Sum function yields inconsistent results in footer

Hello,

I have a report (Access 97) that contains two grouping headers  .  In the footer header of the Fullname group, I've added a calculated field that sums the work hours for all the OBS that are group by the fullname.  I've set the controlsource of the calculated field to = Sum([TotalWorkHours])   However I'm not getting the correct sums

FullName
     OBS      TotalWorkHOurs
chtullu135Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Helen FeddemaConnect With a Mentor Commented:
Also, make sure that you give your controls (or at least, any that are referenced in code) different names than their bound fields, to avoid circular reference errors.
0
 
Helen FeddemaCommented:
Use a textbox in the group footer with Sum() wrapped around the expression that calculates TotalWorkHours.  Here is an example, using TotalPrice:

=Sum(Nz([UnitPrice])*Nz([Quantity]))
0
 
chtullu135Author Commented:
I'm not calculating work hours.  Work hours come from the query that feeds the report.   In my example, I am using =Sum([TotalWorkHours]).  
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
Helen FeddemaConnect With a Mentor Commented:
My LNC Rename add-in helps in the renaming process.  The Access 97 version (if you are still using that version) may be downloaded from this link:
http://www.helenfeddema.com/Files/code4.zip

Access 2000-2003 version:
http://www.helenfeddema.com/Files/code10.zip

Access 2007-2010 version:
http://www.helenfeddema.com/Files/code63.zip

0
 
Helen FeddemaCommented:
Is TotalWorkHours a calculated field in the report's record source?  If it is displayed in a control, what is the control's name?
0
 
Helen FeddemaConnect With a Mentor Commented:
If TotalWorkHours is a calculated field in the record source, and if it is not displayed in a control with that same name, using Sum([TotalWorkHours] (or Sum(Nz([TotalWorkHours])) should work (in the group footer).
0
 
chtullu135Author Commented:
Hello Helen,
TotalWorkHours is not a calculated field.I've also changed the name of the control to txtTotalWorkHours.  I'm still getting inconsistent results
0
 
Jeffrey CoachmanMIS LiasonCommented:
1. "I have a report (Access 97) that contains two grouping headers "
I believe you only mentioned "Full Name", what is the other, ...and what is the Hierarchy order?
If you have two groupings, then your sum will have to be in the Group footer of the outer-most group.

2. Can you please clearly define "inconsistent results"?
Wrong results always?
Wrong results on some records
Wrong results at random?
...ect

3. A picture is worth a thousand words".
Can you post a sample of this DB, and along with this, clearly the *exact* output you are expecting.
Sample database notes:
1. Back up your database(s).
2. Combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Delete any objects that do not relate directly to the issue.
5. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
6. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
7. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
8. Compile the code. (From the database window, click: Debug-->Compile)
9. Run the compact/Repair utility.
10. Remove any Passwords and/or security.
11. Post explicit steps to replicate the issue.
12. Test the database before posting.

In other words, ...post a database that we can easily open and immediately see the issue.

Thanks

JeffCoachman

0
 
chtullu135Author Commented:
Hello Helen,

I went back and redesigned the underlying query.  The original query seemed overly complex and consisted of multiple nested queries including an aggregation query.  When I simplified the design, the error disappeared.  I'm in the process of throughly testing the report to confirm that the problem is indeed fixed
0
 
chtullu135Author Commented:
Although I solved my problem, you gave me some useful tips. Thanks again
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.