here's my SSRS chart::
I've checked the sql statements from which this chart is generated. i've run the statements in SSMS, and they return data without errors.
also, i've used sql profiler to intercept the exact statements that is being sent to sql server, and i've re-run these statements without problems.
what might be some other causes of error in the expression of the source of a chart on ssrs 2008 r2?
this is in design mode:
these are called chart series labels
There is nothing wrong with your SQL otherwise you would not see a report, let a lone a chart on the report. The issue is then in the expression.
The best method for putting in data labels is to use the pre-defined keywords. I suggest you enter #VALY as text in the properties box. For more keywords see MSDN.
Add guide:
Open the label properties dialog box.
Under the label text, see below, change the «Expr» to #VALY.
Dialog box example from google and SearchSQLServer
Related
I am trying to use the current versions of SQL Server Management Studio with Microsoft SQL Server Express (64-bit) to create a Stored procedure.
I’m following the https://msdn.microsoft.com/en-us/library/ms345415.aspx guideline.
When I get to step 3 and right-click on “Stored Procedures” the popup menu I am presented with does not include the “New Stored Procedure” option. Instead, at the top of the list of options that are presented is the option “Stored procedure…” When I click on this I get the ASCI text block “Template Generated from Template Explorer” displayed.
What I was expecting was that the “Specify Values for Template Parameters” Query Editor Pane would have been displayed and that the data I entered into it would have been reflected in the “Template generated from Template Explorer” text block which would have been displayed next.
Can anyone tell me why the “Specify Values for Template Parameters” Query Editor Pane isn’t being displayed?
You can call that dialog by using the key combination Ctrl-Shift-M.
Most likely they are not showing this dialog automatically anymore, in order to let the user change the script first and then call the dialog when ready.
New query tab in CTRL+K,CTRL+X, you can use the combination.
Seems like this is has been asked a few times before.
After working on a form for a few weeks, I suddenly get the error when I click on a button: "The expression On Click you entered as the event property produced the following error: A problem occurred while Microsoft Access was communicating with the OLE Server or Active X Control."
This also happens with any control's event on the form (e.g. After Update on other text fields)
I tried re-installing Access to no avail.
Not sure if this is relevant, but I have a subform on the form as well. I have an "on-click" event that works on the subform, but when the code breaks at the following line (which worked before):
Me.Parent.orderID = Null
The error I get is: "Method 'Parent' of object '_Form_frmOrderQuery' failed
(frmOrderQuery is the name of the subform)
Anyway, this all worked before until I changed the query for the subform by adding a few more fields.
Finally: All of the event handlers (button click, after-update, etc) work on my other forms in the database.
Any help/suggestions would be greatly appreciated.
Thanks,
jeff
Figured it out, this was stupid easy. Whatever Form is having issues, just copy it and delete the old form. Rename the new form to the same as the last (so all your vba and stuff works). Done!
I've just run into a similar problem using the Access runtime environment. It seems that the problem might be with... non-Unicode lanuage settings.
Maybe the names of the columns you added to the query contain some problematic characters?
See this article for reference: https://support.microsoft.com/en-us/kb/907337. It contains a resolution, which helped me.
All the best!
As other users mentioned the problem is in use of non-English symbols in element (form control, etc.) names.
My way to solve it:
(may be unnecessary) Create an event procedure for any element on a form.
Switch to Code Editor.
Place cursor inside any procedure.
Open drop-down list with element names (the left one above the code window).
Check if you see some names with "?????" in them.
If 5 is true, then figure out what the elements are, find them on the form and rename using only basic latin alphabet.
In my case this issue occured because of accented characters.
I was running the VBA code on a computer that uses different non-Unicode language settings than the computer on which i created the event handler, the function, or the subroutine. Note This issue may also occur if the VBA code contains accented characters or special characters. Additionally, this issue may occur if an object name in the Access database contains accented characters or special characters.
The Solution that worked for me:
"If you are running the VBA code on a Microsoft Windows XP-based computer or on a Windows 2000-based computer, you may be able to resolve this issue by changing the non-Unicode language setting on the computer where you are running the VBA code. To verify and to change the non-Unicode language setting, follow these steps.
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
Click Start,
click Run,
type Intl.cpl, and then click OK.
Under Language for non-Unicode programs on the Advanced tab, verify that the language matches the language on the computer on which you created the event handler, the function, or the subroutine. If the language differs, click the language that you want, and then click OK.
Restart the computer.
More here https://support.microsoft.com/en-us/help/907337/you-receive-an-error-message-when-you-start-visual-basic-for-applicati
I am having an issue getting my sub-report to show up in Pentaho Report Designer.
I have actually followed all steps described in a tutorial, but I still can't see my chart in the preview.
I don't know if I need to activate an option or not.
Check that you have you imported your fields (and perhaps parameters) from the main report into the subs. Often this would be the case a sub-report fails to show.
Is it possible to hide a field in a SQL 2008 Report, based on the value of a parameter? I'm leaning towards a custom application and if push comes to shove I'll have do manually code each piece, but I would like to leverage SSRS as much as possible. I've included a screen shot of the report before it is populated. The area in red is what I would like to hide say, =iif(X=1,true,false)
Set up the Expression In Text box Property >> Visibility >> Show or Hide on axpression.
=iif(X=1,true,false)
Hope this help..
Look for the screen shot and more detail click here
using SSRS manager, Parameter field cannot hide programtically. but you can create asp.net webform with SSRS report. MSDN link
I'm currently trying to create a JasperReport report with some special input control behaviour. My needs are:
four input controls, two of them are dateboxes, the other ones are radio buttons
depending on radio button choice, one of the databoxes should be visible or not
so if option 1 is chosen, show both dateboxes; if option 2 is chosen, show only one datebox
I wonder if there's a "clean" solution - didn't find anything.
Any pointers will be helpful.
The Print when expression is not relevant for input controls on JasperReports Server.
There is no built-in support for hiding and showing an input control based on the value of a different one. The infrastructure for cascading input controls can certainly be extended to achieve this... but it would not be trivial.
The path I would take is to customize the .jsp page that displays the input control. There is a section in the JasperReports Server Ultimate Guide called "Customizing the Input Controls Form" which would get you started down this path.
For datebox part, you can use print when expression to decide whether certain blocks of the report is visible.
For other "input", if you meant some data you want to display inside the report, you can make some Parameter in your report, then set the Parameter from user input before you export the report.