Viewing 15 posts - 16 through 30 (of 120 total)
I don't believe so as I believe it only use's the 2003 rendering engine. Have you tried renaming the .xls output to the .xlsx?
Let me know if you...
April 20, 2010 at 9:14 am
I wasn't aware of a limit on the textbox, is it being outputted (as there is a limit in excel cells) into excel or being cut off when being rendered...
April 20, 2010 at 9:11 am
Use the "Row_Number()" function in your SQL Proc or query as a new field as shown here:
SELECT
ROW_NUMBER() OVER (ORDER BY [datActualDate] ASC) AS ROWID,
[datActualDate]
FROM
[Schema].[TableName]
April 20, 2010 at 2:18 am
Yes there is, when creating the dataset there is a timeout option which by default is 30 secs, change to 0 for unlimited...
April 19, 2010 at 11:47 pm
Not a problem at all... Just wait till you start playing with visibility and page numbers, outputting etc using sub reports.... All i have to say is migrane!!!
April 19, 2010 at 9:34 am
Not that i know of, however be aware of how this would look in Excel (which wouldn't fit) or PDF, or even the time it would take to run the...
April 19, 2010 at 9:13 am
The excel output use's the default cell height which is 12.75. So the first line would be displayed but the second, third etc would be hidden. Have you tried exporting...
April 19, 2010 at 8:07 am
Looks like you would be best doing this in SQL first, before it gets into your dataset in the report.
April 19, 2010 at 8:04 am
You need to set its control visibility. I have attached a screenshot as an example, hope this helps...
April 19, 2010 at 7:52 am
We had the same problem, so we created the following function to properly convert the parameters...
******************************************************************************
******************************************************************************
USE [InsertDatabaseName]
GO
/*** BEGIN CREATE FUNCTION [Insert Schema Name].[funcParseInputStringToTable] ***/
CREATE FUNCTION [Insert Schema Name].[funcParseInputStringToTable]
(@InputString...
April 19, 2010 at 7:34 am
The settings you applied dictate the page sizing, it doesn't force your tables and graphs into those sizings... So if you have the A4 settings in the layout properties, you...
April 19, 2010 at 7:23 am
Unfortunately that error message is a little vague however take the following steps...
1. Run the report (that is used in the sub report) in Visual Studio ensuring it works...
2. Build...
April 19, 2010 at 7:18 am
I believe this can be done with XML StyleSheeting, but otherwise I don't think it can be done... Let me know if you do find anything that works!
November 6, 2009 at 9:11 am
You need to use the FORMAT command in the expression builder so example is "=FORMAT(YourfieldName, "MMM yyyy").
November 6, 2009 at 9:06 am
Hi, I am using NVARCAHR 255 in my destination tables, I have tried sting, byte stream and T Weaterun (unicode)
June 27, 2009 at 11:25 am
Viewing 15 posts - 16 through 30 (of 120 total)