Rdlc report formula not working when export to excel

Question

1.00/5 (1 vote)

See more:

VS2013

In vs 2008 i have do it is working

When i export to excel is working

=(ReportItems!Balance2.Value + ReportItems!Supply3.Value) - ReportItems!Demand3.Value

In vs 2013 i am doing it is working

Same code i have used but is not working

=(ReportItems!Balance2.Value + ReportItems!Supply3.Value) - ReportItems!Demand3.Value

Please help me regrading this.

Posted 2-Jul-15 21:18pm

subbuksr123

Updated 6-Jul-15 18:15pm

v2

Add a Solution

Comments

manognya kota 3-Jul-15 6:46am

correct me if iam wrong.As i understand, you are using the same formula "=(ReportItems!Balance2.Value + ReportItems!Supply3.Value) - ReportItems!Demand3.Value" in your VS 2013. it works. but when you export to excel is doesnt work?

subbuksr123 6-Jul-15 1:55am

yes

virusstorm 10-Jul-15 12:22pm

Where and how are you assigning this equation?

subbuksr123 10-Jul-15 12:23pm

in rdlc report viewer

virusstorm 10-Jul-15 13:10pm

Just making sure I understand the issue. So in VS2008, when you export the report to Excel, the equation is in the excel file. The cell in question would have a value like this "=(A1 + B2) - C3".

When you export it using VS2013, the cell in question has a value of "123" instead of the equation.

Am I describing the problem right?

subbuksr123 14-Jul-15 2:04am

Yes.

When I export the report from VS2008, I am getting it in equation form (_746+_756+_766).

When I export the report from VS2013, I am getting it in number "123".

subbuksr123 5-Aug-15 5:50am

any solutions.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)