Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.
COURSE of the MONTH
15 days, 1 hour left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Problem with total in footer of form - #Error
Posted on 2012-12-22
I’ve had problems with subtotals in forms in the past but always have been able to resolve them by going over syntax with a fine-toothed comb and finding an error on my part. In this case I have done that for hours and cannot figure out what I am doing wrong. Here is the scenario:
Access 2013 linking to MS SqlServer database view.
Field is ‘CalculatedValue’, placed in a text box ‘PrintTime’ . The field displays the correct values one each row.
In a text box on the form footer, I use the control source =sum([CalculatedValue]) and get #Error
.
I can replace that control source with =[CalculatedValue] and get the value of whichever row is active. But as soon as I edit the controlsource to =Sum([CalculatedValue]), the #Error returns.
What am I doing wrong?
(NB: I upgraded to 2013 today just to see if it would resolve this issue or at least have better error description to help...)
Access 2013 linking to MS SqlServer database view.
Field is ‘CalculatedValue’, placed in a text box ‘PrintTime’ . The field displays the correct values one each row.
In a text box on the form footer, I use the control source =sum([CalculatedValue]) and get #Error
.I can replace that control source with =[CalculatedValue] and get the value of whichever row is active. But as soon as I edit the controlsource to =Sum([CalculatedValue]), the #Error returns.
What am I doing wrong?
(NB: I upgraded to 2013 today just to see if it would resolve this issue or at least have better error description to help...)
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4-
4
9 Comments
Active today
You can't sum a calculated field.
Try summing the expression that defines the calculated field instead.
Try summing the expression that defines the calculated field instead.
I realize that the name of this column (CalculatedValue) is confusing, but it is NOT a calculated field. That is just the name of the column, it refers to the fact that the underlying data is calculated before being written to the table.
I didn't design this database...
Thanks anyway.
I didn't design this database...
Thanks anyway.
No,I don't think so - data type is number:
I can run this query in Access and it returns the correct number:
SELECT sum(calculatedvalue) as totaltime from dbo_vCyrTransHdrdetParts
the linked table is actually a view in Sqlserver - that would not have any effect would it?
I can run this query in Access and it returns the correct number:
SELECT sum(calculatedvalue) as totaltime from dbo_vCyrTransHdrdetParts
the linked table is actually a view in Sqlserver - that would not have any effect would it?
Actually, to be more specific, the record source for this form is an Access query which is base on the Sqlserver query + one calculated column... not the column in question however.
Just in case any of that matters...
Just in case any of that matters...
Active today
Try this to isolate this and rule out other possible issues with your form...
Create a new form bound to the same recordsource and just add that one textbox, summing that field in your forms footer section.
Create a new form bound to the same recordsource and just add that one textbox, summing that field in your forms footer section.
Good idea, I had just decided to do essentially the same thing myself - started from scratch on the form and it worked just fine. This was a redesign and I reformatted an existing form - apparently a bad idea which undoubtedly cost me far more time than it ever saved...
Thanks for the suggestion!
Thanks for the suggestion!
Active today
Hmm... the test that you ran was directly on your sql table, but you mentioned your form being bound to an Access query.
Try running that same test (your sum query) against the Access query that your form is bound to
Try running that same test (your sum query) against the Access query that your form is bound to
Featured Post
How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening. This article shows how to create and use them.
If you need a simple but flexible process for maintaining an audit trail of who created, edited, or deleted data from a table, or multiple tables, and you can do all of your work from within a form, this simple Audit Log will work for you.
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…
Suggested Courses
Course of the Month15 days, 1 hour left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.