I'm making a report in Reporting services. I have a column in milliseconds and I want to make it as dd:hh:mm.
With Microsoft Analysis Services you can use any VBA function in your MDX, so the whole range of string and date formatting methods are available to you. Perhaps start your MDX with:
WITH MEMBER [Measures].[MyNewName] AS 'FormatDateTime([Measures].[MyExistingName], something-or-other)'
Alternatively, Google FORMAT_STRING and see if that can help.
Related
How can I express the following condition using Timing: "make some prescription three days after encounter start date, 1 tab x 3 times per day"?
(I understand how to express the latter part of the expression, as the authors provided Timing documentation with an example).
The relativeDate extension allows you to specify a date as relative to some other date.
HL7 Pharmacy Work Group is planning changes to the Dosage type used in FHIR to support "conditional doses" such as this one. Currently this is not supported in FHIR.
First of, is there any real documentation of the toolkit ? What I would like is to specify a range of selectable dates. For example I don't want to display dates before today. If the user select a start date of Jan. 27th 2012, I want to allow only dates after these for the return date
Documentation is a little bit sparse for the toolkit - your best bet is to look in the source of the sample app but they don't cover all the scenarios.
The default control doesn't seem to support a minimum or maximum value for the selected date, but if you download the source you should be able to modify it according to your needs. The layout of the source is pretty straightforward and you should be able to find an acceptable place to add the code, the only thing you need to decide is how you handle it from a UI perspective. In my opinion, you are better off handling the range check once the control returns - if it is an invalid date, pop up a message and re-show the control.
I've found that in the absence of documentation, the WindowsPhoneGeek blog (in this specific case see link here) usually does a good job of explaining the Silverlight Toolkit components in their various articles.
These articles can be a great help when following ZombieSheep's advice of taking a look at the toolkit sample code.
First of, is there any real documentation of the toolkit ? What I would like is to specify a range of selectable dates. For example I don't want to display dates before today. If the user select a start date of Jan. 27th 2012, I want to allow only dates after these for the return date
Documentation is a little bit sparse for the toolkit - your best bet is to look in the source of the sample app but they don't cover all the scenarios.
The default control doesn't seem to support a minimum or maximum value for the selected date, but if you download the source you should be able to modify it according to your needs. The layout of the source is pretty straightforward and you should be able to find an acceptable place to add the code, the only thing you need to decide is how you handle it from a UI perspective. In my opinion, you are better off handling the range check once the control returns - if it is an invalid date, pop up a message and re-show the control.
I've found that in the absence of documentation, the WindowsPhoneGeek blog (in this specific case see link here) usually does a good job of explaining the Silverlight Toolkit components in their various articles.
These articles can be a great help when following ZombieSheep's advice of taking a look at the toolkit sample code.
I get the type not defined error for XlEnableCancelKey when trying to use ShellAndWait with MS Word VBA. The Xl part of XlEnableCancelKey looks like it maybe an MS Excel type.
Also asked on MSDN VBA Forum.
Yes
In the VBA project, add a reference to the Microsoft Excel 12.0 Object Library.
Use WdEnableCancelKey instead of XlEnableCancelKey.
The reason being, for word a different enum type is defined which is used for Application.EnableCancelKey.
EDIT: Having looked at the link, I saw this line.
Application.EnableCancelKey = xlErrorHandler
Effectively, the code is wanting to use an enum value for EnableCancelKey.
Hence, you can use WdEnableCancelKey in place of XlErrorHandler.
I'm new to SSRS, so I apologize if this question is too simple:
I have a report which accepts a parameter called "Amount". I want to constrain valid inputs to currency values >= 0, and pop open an error message if the user enters improper values.
I don't want to validate inputs in my stored procedure and throw exceptions, because SSRS displays a very generic "Query execution failed for 'someTable'" message to users who access the report from another machine, and my business does not want to turn on the "Enable Remote Errors" flag.
How do I add input validation to report parameters and notify users of bad input?
Yes, I've googled around, but haven't had much luck. Thanks in advance :)
Okay, how about this?
All you have in SSRS, really, is the SQL query and expressions in report fields.
Perhaps you could add a big, red text box at the top of the report for your error message, and give it an expression like '=IIf(Parameters!Amount.Value < 0, "Error: Invalid Amount", "")'.
Then go to your table's "Hidden" property and give it the expression "=Parameters!Amount.Value < 0"
You could also add into your query's where clause and add "AND #Amount >= 0" so you aren't fetching from the database when there's an error.
It's possible to make report parameters in SSRS that are based on a particular list or a lookup query but I don't think you can apply a regex or something like that.
Instead you might consider separating your report into two panels, one which displays your report and one which displays an error and then you create an assembly with a function in it that validates the parameters for the report before it is run. If the validate parameters function is successful you hide the error panel and show the report panel, if not you do the opposite.
I don't think there's a whole lot you can do in the reporting tool itself. It's pretty rudimentary.
However, you can provide an ASP.net web interface or a form that you can use to ask the users for the parameter values in any format .NET allows, and use the ReportViewer control to display the report. It sounds daunting, but it's actually pretty straight-forward, particularly if you already have a project you can build on.
Microsoft gives tutorials for using the ReportViewer controls.