Showing posts with label field. Show all posts
Showing posts with label field. Show all posts

Tuesday, March 27, 2012

Can not insert input field with length gt 128

I got this problem that really puzzled me. I used a stored procedure to
insert records into SQL. When the field of input string contained more than
128 characters, it gave me this message:
The identifier that starts with 'Today is a nice day..........Good bye'
is too long. Maximum length is 128.
But here I am not sending in an identifier name, I am sending in the actual
input which is more than 128 characters long. The input field in the data
base is defined as varchar(1000).
Any ideas?What is the size on the parameter declaration in the stored procedure? I'll
bet you a shiny new nickel it's VARCHAR(128) or CHAR(128).
"pelican" <pelican@.discussions.microsoft.com> wrote in message
news:D4B955D4-C318-4E38-BB9F-77B439561881@.microsoft.com...
>I got this problem that really puzzled me. I used a stored procedure to
> insert records into SQL. When the field of input string contained more
> than
> 128 characters, it gave me this message:
> The identifier that starts with 'Today is a nice day..........Good bye'
> is too long. Maximum length is 128.
> But here I am not sending in an identifier name, I am sending in the
> actual
> input which is more than 128 characters long. The input field in the data
> base is defined as varchar(1000).
> Any ideas?|||> What is the size on the parameter declaration in the stored procedure?
> I'll bet you a shiny new nickel it's VARCHAR(128) or CHAR(128).
Actually, it sounds like the call he is making to the database doesn't
properly encapsulate this string. It seems SQL Server has mistaken the
string for an identifier (otherwise the error would be "string or binary
data would be truncated"). This usually happens when someone uses " instead
of ' for delimiting a string, but there are other possibilities as well.
"pelican", how about showing us the actual code you are using, instead of
vaguely describing it -- then we don't have to guess. I suppose DDL for the
table you are trying to INSERT into wouldn't hurt either (see
http://www.aspfaq.com/5006).|||Good point, probably an embedded ' in the input somewhere that wasn't
properly escaped by the app. Interesting that it would pick 128 as the
cut-off size, however. I would definitely need to see the code for the SP
and the input string.
"AB - MVP" <ten.xoc@.dnartreb.noraa> wrote in message
news:u6KSE6AUFHA.2712@.TK2MSFTNGP09.phx.gbl...
> Actually, it sounds like the call he is making to the database doesn't
> properly encapsulate this string. It seems SQL Server has mistaken the
> string for an identifier (otherwise the error would be "string or binary
> data would be truncated"). This usually happens when someone uses "
> instead of ' for delimiting a string, but there are other possibilities as
> well.
> "pelican", how about showing us the actual code you are using, instead of
> vaguely describing it -- then we don't have to guess. I suppose DDL for
> the table you are trying to INSERT into wouldn't hurt either (see
> http://www.aspfaq.com/5006).
>|||> Good point, probably an embedded ' in the input somewhere that wasn't
> properly escaped by the app. Interesting that it would pick 128 as the
> cut-off size, however.
That is the maximum size for an identifier. I don't think it is an errant
', it just received this string that it thinks is supposed to be a column,
and is saying, WHOA, this column name is bigger than 128, hold on. It could
be 129 or 8000 characters... the same error will get kicked out.|||Thank you all so much! "AB - MVP" is right, once I changed the double quote
(") to single ('), it worked fine! In the stored procedure, the size on the
parameter is varchar(1000). I did not realize that the "" sign will make SQ
L
believe I was passing an identifier instead of the actually content.
You are my life saver...
"AB - MVP" wrote:

> Actually, it sounds like the call he is making to the database doesn't
> properly encapsulate this string. It seems SQL Server has mistaken the
> string for an identifier (otherwise the error would be "string or binary
> data would be truncated"). This usually happens when someone uses " inste
ad
> of ' for delimiting a string, but there are other possibilities as well.
> "pelican", how about showing us the actual code you are using, instead of
> vaguely describing it -- then we don't have to guess. I suppose DDL for th
e
> table you are trying to INSERT into wouldn't hurt either (see
> http://www.aspfaq.com/5006).
>
>|||I read about the identifier length in the help section. It said the same
thing as AB-MVP pointed out, that 128 is the maximum length per row for an
identifier. I just never dreamed that a " will do it.
Thanks a lot!|||Yeah it's called a "quoted identifier" and can be circumvented by using
"parameterized queries".
"pelican" <pelican@.discussions.microsoft.com> wrote in message
news:6F3F8CAB-1EBD-45A6-BF74-4DC272EA1804@.microsoft.com...
> Thank you all so much! "AB - MVP" is right, once I changed the double
> quote
> (") to single ('), it worked fine! In the stored procedure, the size on
> the
> parameter is varchar(1000). I did not realize that the "" sign will make
> SQL
> believe I was passing an identifier instead of the actually content.
> You are my life saver...
> "AB - MVP" wrote:
>|||Yep that's what they get for slapping a SQL statement together with +'s
instead of using parameterized queries.
"AB - MVP" <ten.xoc@.dnartreb.noraa> wrote in message
news:uGWbvCBUFHA.1896@.TK2MSFTNGP14.phx.gbl...
> That is the maximum size for an identifier. I don't think it is an errant
> ', it just received this string that it thinks is supposed to be a column,
> and is saying, WHOA, this column name is bigger than 128, hold on. It
> could be 129 or 8000 characters... the same error will get kicked out.
>

Tuesday, March 20, 2012

Can not change filter on model report - UPDATED 7th June

I have a very simple report based on a test model.

The report is filtered via a date field and runs ok.

If I try to change the filter I get the following error message:

Operation Failed

Short time pattern does not include hours and minutes

Does anyone know how I can correct this?

Regards

John

UPDATE

This only happens if I try to filter between two dates, a single date works correctly!

Can you please save report that fails to file and post it?|||

Alexandre

This is the rdl for the failing report.

<?xml version="1.0" encoding="utf-8"?>

<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

<Language>en-US</Language>

<BottomMargin>0.5in</BottomMargin>

<RightMargin>0.5in</RightMargin>

<DataSets>

<DataSet Name="dataSet">

<Query>

<DataSourceName>dataSource1</DataSourceName>

<CommandText>&lt;SemanticQuery xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:rb="http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder" xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"&gt;

&lt;Hierarchies&gt;

&lt;Hierarchy&gt;

&lt;BaseEntity&gt;

&lt;!--Epex Referral--&gt;

&lt;EntityID&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/EntityID&gt;

&lt;/BaseEntity&gt;

&lt;Groupings&gt;

&lt;Grouping Name="Epex Referral"&gt;

&lt;Expression Name="Epex Referral"&gt;

&lt;EntityRef&gt;

&lt;!--Epex Referral--&gt;

&lt;EntityID&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/EntityID&gt;

&lt;/EntityRef&gt;

&lt;/Expression&gt;

&lt;Details&gt;

&lt;Expression Name="Created"&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="Close Date"&gt;

&lt;AttributeRef&gt;

&lt;!--Close Date--&gt;

&lt;AttributeID&gt;G36ac2614-9e79-4c60-9c3e-fc45de7c67ec&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="Patient"&gt;

&lt;Path&gt;

&lt;RolePathItem&gt;

&lt;!--Patient--&gt;

&lt;RoleID&gt;G036974d5-33a0-4096-bc96-166d82853818&lt;/RoleID&gt;

&lt;/RolePathItem&gt;

&lt;/Path&gt;

&lt;AttributeRef&gt;

&lt;!--Name--&gt;

&lt;AttributeID&gt;Gd6622d3c-8a4f-4273-a190-c8834bf90031&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="expr1"&gt;

&lt;AttributeRef&gt;

&lt;!--Updated--&gt;

&lt;AttributeID&gt;Gfee3c95d-eb72-48c3-b372-0e2865ac44c8&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;/Details&gt;

&lt;/Grouping&gt;

&lt;/Groupings&gt;

&lt;Filter&gt;

&lt;Expression Name="expr2"&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;GreaterThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2005-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;LessThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2006-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:FilterCondition" /&gt;

&lt;CustomProperty Name="qd:Filter" /&gt;

&lt;CustomProperty Name="qd:ContextEntityID"&gt;

&lt;Value xsi:type="xsd:string"&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;

&lt;CustomProperty Name="qd:Design"&gt;

&lt;Value xsi:type="xsd:string"&gt;expr3&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/Filter&gt;

&lt;/Hierarchy&gt;

&lt;/Hierarchies&gt;

&lt;CalculatedAttributes&gt;

&lt;Expression Name="expr3"&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;GreaterThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2005-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;LessThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2006-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:FilterCondition" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Null /&gt;

&lt;CustomPropertes&gt;

&lt;CustomProperty Name="qd:Unspecified" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:Filter" /&gt;

&lt;CustomProperty Name="qd:ContextEntityID"&gt;

&lt;Value xsi:type="xsd:string"&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/CalculatedAttributes&gt;

&lt;/SemanticQuery&gt;</CommandText>

</Query>

<Fields>

<Field Name="EpexReferral">

<DataField>Epex Referral</DataField>

</Field>

<Field Name="Created">

<DataField>Created</DataField>

</Field>

<Field Name="CloseDate">

<DataField>Close Date</DataField>

</Field>

<Field Name="Patient">

<DataField>Patient</DataField>

</Field>

<Field Name="expr1">

<DataField>expr1</DataField>

</Field>

</Fields>

</DataSet>

</DataSets>

<DataSources>

<DataSource Name="dataSource1">

<DataSourceReference>/Models/Mars Cutdown</DataSourceReference>

<rd:DataSourceID>4d1edcd6-3c78-4e68-9566-ef952e495be4</rd:DataSourceID>

</DataSource>

</DataSources>

<PageHeight>11in</PageHeight>

<LeftMargin>0.5in</LeftMargin>

<TopMargin>0.5in</TopMargin>

<Width>7.5in</Width>

<Body>

<Height>0in</Height>

<ReportItems>

<Textbox Name="Title">

<Left>0.5in</Left>

<Top>0.5in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value />

<Style>

<FontFamily>Tahoma</FontFamily>

<TextAlign>Left</TextAlign>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>18pt</FontSize>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:Watermark</Name>

<Value>Click to add title</Value>

</CustomProperty>

</CustomProperties>

<Height>0.375in</Height>

</Textbox>

<Table Name="table">

<Top>1.25in</Top>

<Details>

<TableRows>

<TableRow>

<TableCells>

<TableCell>

<ReportItems>

<Textbox Name="Created_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Action>

<Drillthrough>

<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>

<Parameters>

<Parameter Name="rs:EntityID">

<Value>G066c76f8-9856-4acd-8b54-d734971da2c8</Value>

</Parameter>

<Parameter Name="rs:DrillType">

<Value>Detail</Value>

</Parameter>

<Parameter Name="rs:Command">

<Value>Drillthrough</Value>

</Parameter>

<Parameter Name="DrillthroughSourceQuery">

<Value>=DataSets!dataSet.RewrittenCommandText</Value>

</Parameter>

<Parameter Name="DrillthroughContext">

<Value>=CreateDrillthroughContext()</Value>

</Parameter>

</Parameters>

</Drillthrough>

</Action>

<Value>=Fields!Created.Value</Value>

<Styl>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<Format>d</Format>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="CloseDate_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Value>=Fields!CloseDate.Value</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<Format>d</Format>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="Patient_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Action>

<Drillthrough>

<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>

<Parameters>

<Parameter Name="rs:EntityID">

<Value>G2ceef5ce-4e09-4806-8e8c-9a4e4e8f35fa</Value>

</Parameter>

<Parameter Name="rs:DrillType">

<Value>Detail</Value>

</Parameter>

<Parameter Name="rs:Command">

<Value>Drillthrough</Value>

</Parameter>

<Parameter Name="DrillthroughSourceQuery">

<Value>=DataSets!dataSet.RewrittenCommandText</Value>

</Parameter>

<Parameter Name="DrillthroughContext">

<Value>=CreateDrillthroughContext()</Value>

</Parameter>

</Parameters>

</Drillthrough>

</Action>

<Value>=Fields!Patient.Value</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

</TableCells>

<Height>0.25in</Height>

</TableRow>

</TableRows>

<Grouping Name="table_EpexReferral">

<GroupExpressions>

<GroupExpression>=Fields!EpexReferral.Value</GroupExpression>

</GroupExpressions>

</Grouping>

<Sorting>

<SortBy>

<SortExpression>=IIf(True, Fields!expr1.Value, Nothing)</SortExpression>

<Direction>Descending</Direction>

</SortBy>

<SortBy>

<SortExpression>=IIf(True, Fields!Created.Value, Nothing)</SortExpression>

<Direction>Descending</Direction>

</SortBy>

</Sorting>

</Details>

<Style />

<Width>0in</Width>

<Height>0in</Height>

<DataSetName>dataSet</DataSetName>

<TableColumns>

<TableColumn>

<Width>0.90092in</Width>

<Visibility>

<Hidden>=Fields!Created.IsMissing</Hidden>

</Visibility>

</TableColumn>

<TableColumn>

<Width>1.06361in</Width>

<Visibility>

<Hidden>=Fields!CloseDate.IsMissing</Hidden>

</Visibility>

</TableColumn>

<TableColumn>

<Width>1.62189in</Width>

<Visibility>

<Hidden>=Fields!Patient.IsMissing</Hidden>

</Visibility>

</TableColumn>

</TableColumns>

<Header>

<TableRows>

<TableRow>

<TableCells>

<TableCell>

<ReportItems>

<Textbox Name="Created_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!Created.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Created</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="CloseDate_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!CloseDate.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Close Date</Value>

<Style

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="Patient_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!Patient.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Patient</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

</TableCells>

<Height>0.25in</Height>

</TableRow>

</TableRows>

<RepeatOnNewPage>true</RepeatOnNewPage>

<FixedHeader>true</FixedHeader>

</Header>

<Left>0.5in</Left>

</Table>

<Textbox Name="TotalRows">

<Left>0.5in</Left>

<Top>3in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value>=String.Format("Total Epex Referrals" &amp; Chr(58) &amp; " {0}", COUNTROWS("dataSet"))</Value>

<Style>

<PaddingLeft>3pt</PaddingLeft>

<PaddingBottom>3pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<PaddingRight>3pt</PaddingRight>

<PaddingTop>3pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:SpecialContent</Name>

<Value>TotalRows</Value>

</CustomProperty>

</CustomProperties>

<Height>0.25in</Height>

</Textbox>

<Textbox Name="FilterDescription">

<Left>0.5in</Left>

<Top>3.5in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value>Filter: Epex Referrals with: Created from 01/01/2005 to 01/01/2006</Value>

<Style>

<PaddingLeft>3pt</PaddingLeft>

<PaddingBottom>3pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<PaddingRight>3pt</PaddingRight>

<PaddingTop>3pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:SpecialContent</Name>

Value>FilterDescription</Value>

</CustomProperty>

</CustomProperties>

<Height>0.25in</Height>

</Textbox>

</ReportItems>

<Style />

</Body>

<PageWidth>8.5in</PageWidth>

</Report>

|||

Is this error happening when you are editing report or when you are running this report? Can you save this report to report server and run it from Report Manager (http://rshost/reports)?

Thanks!

|||

The report executes with no problems, I only get the error if I try to change the filter.

What is strange, I can get around the error by apply to separate date filters, one using Greater Than Or Equal and the other Less Than or Equal.

This gets around the problem but I would like to offer my end users the option of From and To as this is what the use in other parts of SSRS.

Regards

John

|||

We have the same problem even after installing SP1 and the hotfixes. Has anybody a solution/answer?

Regards

Werner

|||This is a known issue that will be fixed in SP2. Unfortunately the only way to avoid this error for now is to change your Windows regional settings to use a 12-hour clock.|||

Bob,

thanks for the immediate answer, when can we approx. expect SP2?

Regards

Werner

|||No committed dates yet, but I believe it's on track for later this year.|||

Bob,

i tried to change the format in the regional settings like you said but no changes. We use a german W2003 server... When i select a date field in the report builder filter, select a date from the datetime picker (22.06.2006) and try to save it with the ok button i get a message box saying 'no valid date'...?!?

Can i change anything in the model to solve the problem? Is this filter problem caused by SP1 (in this case we could think about setting up the SQL Server again)?

Regards

Werner

Can not change filter on model report - UPDATED

I have a very simple report based on a test model.

The report is filtered via a date field and runs ok.

If I try to change the filter I get the following error message:

Operation Failed

Short time pattern does not include hours and minutes

Does anyone know how I can correct this?

Regards

John

UPDATE

This only happens if I try to filter between two dates, a single date works correctly!

Can you please save report that fails to file and post it?|||

Alexandre

This is the rdl for the failing report.

<?xml version="1.0" encoding="utf-8"?>

<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">

<Language>en-US</Language>

<BottomMargin>0.5in</BottomMargin>

<RightMargin>0.5in</RightMargin>

<DataSets>

<DataSet Name="dataSet">

<Query>

<DataSourceName>dataSource1</DataSourceName>

<CommandText>&lt;SemanticQuery xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:rb="http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder" xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"&gt;

&lt;Hierarchies&gt;

&lt;Hierarchy&gt;

&lt;BaseEntity&gt;

&lt;!--Epex Referral--&gt;

&lt;EntityID&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/EntityID&gt;

&lt;/BaseEntity&gt;

&lt;Groupings&gt;

&lt;Grouping Name="Epex Referral"&gt;

&lt;Expression Name="Epex Referral"&gt;

&lt;EntityRef&gt;

&lt;!--Epex Referral--&gt;

&lt;EntityID&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/EntityID&gt;

&lt;/EntityRef&gt;

&lt;/Expression&gt;

&lt;Details&gt;

&lt;Expression Name="Created"&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="Close Date"&gt;

&lt;AttributeRef&gt;

&lt;!--Close Date--&gt;

&lt;AttributeID&gt;G36ac2614-9e79-4c60-9c3e-fc45de7c67ec&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="Patient"&gt;

&lt;Path&gt;

&lt;RolePathItem&gt;

&lt;!--Patient--&gt;

&lt;RoleID&gt;G036974d5-33a0-4096-bc96-166d82853818&lt;/RoleID&gt;

&lt;/RolePathItem&gt;

&lt;/Path&gt;

&lt;AttributeRef&gt;

&lt;!--Name--&gt;

&lt;AttributeID&gt;Gd6622d3c-8a4f-4273-a190-c8834bf90031&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression Name="expr1"&gt;

&lt;AttributeRef&gt;

&lt;!--Updated--&gt;

&lt;AttributeID&gt;Gfee3c95d-eb72-48c3-b372-0e2865ac44c8&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;/Details&gt;

&lt;/Grouping&gt;

&lt;/Groupings&gt;

&lt;Filter&gt;

&lt;Expression Name="expr2"&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;GreaterThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2005-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;LessThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2006-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:FilterCondition" /&gt;

&lt;CustomProperty Name="qd:Filter" /&gt;

&lt;CustomProperty Name="qd:ContextEntityID"&gt;

&lt;Value xsi:type="xsd:string"&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;

&lt;CustomProperty Name="qd:Design"&gt;

&lt;Value xsi:type="xsd:string"&gt;expr3&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/Filter&gt;

&lt;/Hierarchy&gt;

&lt;/Hierarchies&gt;

&lt;CalculatedAttributes&gt;

&lt;Expression Name="expr3"&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;And&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;GreaterThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2005-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Function&gt;

&lt;FunctionName&gt;LessThanOrEquals&lt;/FunctionName&gt;

&lt;Arguments&gt;

&lt;Expression&gt;

&lt;AttributeRef&gt;

&lt;!--Created--&gt;

&lt;AttributeID&gt;G9a9689b0-64a7-49de-abae-58b8d30322e9&lt;/AttributeID&gt;

&lt;/AttributeRef&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Literal&gt;

&lt;DataType&gt;DateTime&lt;/DataType&gt;

&lt;Value&gt;2006-01-01T00:00:00&lt;/Value&gt;

&lt;/Literal&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:FilterCondition" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;Expression&gt;

&lt;Null /&gt;

&lt;CustomPropertes&gt;

&lt;CustomProperty Name="qd:Unspecified" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/Arguments&gt;

&lt;/Function&gt;

&lt;CustomProperties&gt;

&lt;CustomProperty Name="qd:Filter" /&gt;

&lt;CustomProperty Name="qd:ContextEntityID"&gt;

&lt;Value xsi:type="xsd:string"&gt;G066c76f8-9856-4acd-8b54-d734971da2c8&lt;/Value&gt;

&lt;/CustomProperty&gt;

&lt;CustomProperty Name="qd:AutoChangeBaseEntity" /&gt;

&lt;/CustomProperties&gt;

&lt;/Expression&gt;

&lt;/CalculatedAttributes&gt;

&lt;/SemanticQuery&gt;</CommandText>

</Query>

<Fields>

<Field Name="EpexReferral">

<DataField>Epex Referral</DataField>

</Field>

<Field Name="Created">

<DataField>Created</DataField>

</Field>

<Field Name="CloseDate">

<DataField>Close Date</DataField>

</Field>

<Field Name="Patient">

<DataField>Patient</DataField>

</Field>

<Field Name="expr1">

<DataField>expr1</DataField>

</Field>

</Fields>

</DataSet>

</DataSets>

<DataSources>

<DataSource Name="dataSource1">

<DataSourceReference>/Models/Mars Cutdown</DataSourceReference>

<rd:DataSourceID>4d1edcd6-3c78-4e68-9566-ef952e495be4</rd:DataSourceID>

</DataSource>

</DataSources>

<PageHeight>11in</PageHeight>

<LeftMargin>0.5in</LeftMargin>

<TopMargin>0.5in</TopMargin>

<Width>7.5in</Width>

<Body>

<Height>0in</Height>

<ReportItems>

<Textbox Name="Title">

<Left>0.5in</Left>

<Top>0.5in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value />

<Style>

<FontFamily>Tahoma</FontFamily>

<TextAlign>Left</TextAlign>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>18pt</FontSize>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:Watermark</Name>

<Value>Click to add title</Value>

</CustomProperty>

</CustomProperties>

<Height>0.375in</Height>

</Textbox>

<Table Name="table">

<Top>1.25in</Top>

<Details>

<TableRows>

<TableRow>

<TableCells>

<TableCell>

<ReportItems>

<Textbox Name="Created_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Action>

<Drillthrough>

<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>

<Parameters>

<Parameter Name="rs:EntityID">

<Value>G066c76f8-9856-4acd-8b54-d734971da2c8</Value>

</Parameter>

<Parameter Name="rs:DrillType">

<Value>Detail</Value>

</Parameter>

<Parameter Name="rs:Command">

<Value>Drillthrough</Value>

</Parameter>

<Parameter Name="DrillthroughSourceQuery">

<Value>=DataSets!dataSet.RewrittenCommandText</Value>

</Parameter>

<Parameter Name="DrillthroughContext">

<Value>=CreateDrillthroughContext()</Value>

</Parameter>

</Parameters>

</Drillthrough>

</Action>

<Value>=Fields!Created.Value</Value>

<Styl>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<Format>d</Format>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="CloseDate_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Value>=Fields!CloseDate.Value</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<Format>d</Format>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="Patient_Value">

<DataElementOutput>Output</DataElementOutput>

<CanGrow>true</CanGrow>

<Action>

<Drillthrough>

<ReportName>=DataSources!dataSource1.DataSourceReference</ReportName>

<Parameters>

<Parameter Name="rs:EntityID">

<Value>G2ceef5ce-4e09-4806-8e8c-9a4e4e8f35fa</Value>

</Parameter>

<Parameter Name="rs:DrillType">

<Value>Detail</Value>

</Parameter>

<Parameter Name="rs:Command">

<Value>Drillthrough</Value>

</Parameter>

<Parameter Name="DrillthroughSourceQuery">

<Value>=DataSets!dataSet.RewrittenCommandText</Value>

</Parameter>

<Parameter Name="DrillthroughContext">

<Value>=CreateDrillthroughContext()</Value>

</Parameter>

</Parameters>

</Drillthrough>

</Action>

<Value>=Fields!Patient.Value</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>White</BackgroundColor>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

</TableCells>

<Height>0.25in</Height>

</TableRow>

</TableRows>

<Grouping Name="table_EpexReferral">

<GroupExpressions>

<GroupExpression>=Fields!EpexReferral.Value</GroupExpression>

</GroupExpressions>

</Grouping>

<Sorting>

<SortBy>

<SortExpression>=IIf(True, Fields!expr1.Value, Nothing)</SortExpression>

<Direction>Descending</Direction>

</SortBy>

<SortBy>

<SortExpression>=IIf(True, Fields!Created.Value, Nothing)</SortExpression>

<Direction>Descending</Direction>

</SortBy>

</Sorting>

</Details>

<Style />

<Width>0in</Width>

<Height>0in</Height>

<DataSetName>dataSet</DataSetName>

<TableColumns>

<TableColumn>

<Width>0.90092in</Width>

<Visibility>

<Hidden>=Fields!Created.IsMissing</Hidden>

</Visibility>

</TableColumn>

<TableColumn>

<Width>1.06361in</Width>

<Visibility>

<Hidden>=Fields!CloseDate.IsMissing</Hidden>

</Visibility>

</TableColumn>

<TableColumn>

<Width>1.62189in</Width>

<Visibility>

<Hidden>=Fields!Patient.IsMissing</Hidden>

</Visibility>

</TableColumn>

</TableColumns>

<Header>

<TableRows>

<TableRow>

<TableCells>

<TableCell>

<ReportItems>

<Textbox Name="Created_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!Created.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Created</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="CloseDate_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!CloseDate.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Close Date</Value>

<Style

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

<TableCell>

<ReportItems>

<Textbox Name="Patient_Header">

<CanGrow>true</CanGrow>

<UserSort>

<SortExpression>=Fields!Patient.Value</SortExpression>

<SortExpressionScope>table_EpexReferral</SortExpressionScope>

</UserSort>

<Value>Patient</Value>

<Style>

<Language>en-US</Language>

<BorderColor>

<Default>LightGrey</Default>

</BorderColor>

<BorderStyle>

<Default>Solid</Default>

</BorderStyle>

<FontFamily>Tahoma</FontFamily>

<PaddingLeft>2pt</PaddingLeft>

<PaddingBottom>2pt</PaddingBottom>

<FontWeight>Bold</FontWeight>

<FontSize>8pt</FontSize>

<BackgroundColor>#518ae5</BackgroundColor>

<Color>White</Color>

<PaddingRight>2pt</PaddingRight>

<PaddingTop>2pt</PaddingTop>

</Style>

</Textbox>

</ReportItems>

</TableCell>

</TableCells>

<Height>0.25in</Height>

</TableRow>

</TableRows>

<RepeatOnNewPage>true</RepeatOnNewPage>

<FixedHeader>true</FixedHeader>

</Header>

<Left>0.5in</Left>

</Table>

<Textbox Name="TotalRows">

<Left>0.5in</Left>

<Top>3in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value>=String.Format("Total Epex Referrals" &amp; Chr(58) &amp; " {0}", COUNTROWS("dataSet"))</Value>

<Style>

<PaddingLeft>3pt</PaddingLeft>

<PaddingBottom>3pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<PaddingRight>3pt</PaddingRight>

<PaddingTop>3pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:SpecialContent</Name>

<Value>TotalRows</Value>

</CustomProperty>

</CustomProperties>

<Height>0.25in</Height>

</Textbox>

<Textbox Name="FilterDescription">

<Left>0.5in</Left>

<Top>3.5in</Top>

<CanGrow>true</CanGrow>

<Width>6.5in</Width>

<Value>Filter: Epex Referrals with: Created from 01/01/2005 to 01/01/2006</Value>

<Style>

<PaddingLeft>3pt</PaddingLeft>

<PaddingBottom>3pt</PaddingBottom>

<FontWeight>Normal</FontWeight>

<FontSize>8pt</FontSize>

<PaddingRight>3pt</PaddingRight>

<PaddingTop>3pt</PaddingTop>

</Style>

<CustomProperties>

<CustomProperty>

<Name>rb:SpecialContent</Name>

Value>FilterDescription</Value>

</CustomProperty>

</CustomProperties>

<Height>0.25in</Height>

</Textbox>

</ReportItems>

<Style />

</Body>

<PageWidth>8.5in</PageWidth>

</Report>

|||

Is this error happening when you are editing report or when you are running this report? Can you save this report to report server and run it from Report Manager (http://rshost/reports)?

Thanks!

|||

The report executes with no problems, I only get the error if I try to change the filter.

What is strange, I can get around the error by apply to separate date filters, one using Greater Than Or Equal and the other Less Than or Equal.

This gets around the problem but I would like to offer my end users the option of From and To as this is what the use in other parts of SSRS.

Regards

John

|||

We have the same problem even after installing SP1 and the hotfixes. Has anybody a solution/answer?

Regards

Werner

|||This is a known issue that will be fixed in SP2. Unfortunately the only way to avoid this error for now is to change your Windows regional settings to use a 12-hour clock.|||

Bob,

thanks for the immediate answer, when can we approx. expect SP2?

Regards

Werner

|||No committed dates yet, but I believe it's on track for later this year.|||

Bob,

i tried to change the format in the regional settings like you said but no changes. We use a german W2003 server... When i select a date field in the report builder filter, select a date from the datetime picker (22.06.2006) and try to save it with the ok button i get a message box saying 'no valid date'...?!?

Can i change anything in the model to solve the problem? Is this filter problem caused by SP1 (in this case we could think about setting up the SQL Server again)?

Regards

Werner

sql

Monday, March 19, 2012

Can NEWLINE in FORMAT?

I have a date field and use the format: dd MM/dd/yy
The output is: Fri 10/15/04
I would like this instead:
Fri
10/15/04
Is there a way to add a line break using the simple format codes?
Thanks, JerryI have found that adding
... & chr(10) & chr(13) & ...
seems to do the trick.
"Jerry Nixon" wrote:
> I have a date field and use the format: dd MM/dd/yy
> The output is: Fri 10/15/04
> I would like this instead:
> Fri
> 10/15/04
> Is there a way to add a line break using the simple format codes?
> Thanks, Jerry
>|||I do not know of a way that you can add a line break when typing the format
code into the Format property. It can be done in several ways when using an
expression. For example:
=Format( Fields!YoureDate.Value, "ddd") + ControlChars.crlf + Format(
Fields!YourDate.Value, "MM/dd/yy")
"Jerry Nixon" wrote:
> I have a date field and use the format: dd MM/dd/yy
> The output is: Fri 10/15/04
> I would like this instead:
> Fri
> 10/15/04
> Is there a way to add a line break using the simple format codes?
> Thanks, Jerry
>

Can MSRS render HTML?

Hi,
I have a HTML tags inside on of my dataset's fields. Is there anyway that I
have the contents of the field rendered on the report?
Can I at least extract the pure text from the HTML tags and show them on the
report?
Thank you,
AlanReporting Services currently does not support rich text fields. This is
planned for a future version. You can write a custom function to strip out
the HTML tags.
--
Rajeev Karunakaran [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"A.M" <Hate-Spam@.nowhere.com> wrote in message
news:%231Id6APUFHA.2768@.tk2msftngp13.phx.gbl...
> Hi,
>
> I have a HTML tags inside on of my dataset's fields. Is there anyway that
> I have the contents of the field rendered on the report?
>
> Can I at least extract the pure text from the HTML tags and show them on
> the report?
>
> Thank you,
> Alan
>
>

Thursday, March 8, 2012

Can Iif( do a substring query on a storage field?

Ok,
This is what I don't understand. Hidden rows with downline dealers
only has '5678'. But the visible row that needs a drill down might
have in the dealerlineageid field (which is a field not to be
displayed)
'5678' and '2754' and 10 other dealer numbers (multiple dealer
numbers).
How would I know if '5678' is in there as a string value (which is just
one of the many numbers in that field)? If it has multiple
dealer numbers separated by commas? Wouldn't the expression for the
"hidden" value need to be a substring query? How would I do that?
Thanks,
TrintI always prefer preparing the data from base on. Where do you get the data
you want to render in the report, is there a chance to normalize it before
passing it to the report ?
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"trint" <trinity.smith@.gmail.com> schrieb im Newsbeitrag
news:1113916563.747603.202200@.l41g2000cwc.googlegroups.com...
> Ok,
> This is what I don't understand. Hidden rows with downline dealers
> only has '5678'. But the visible row that needs a drill down might
> have in the dealerlineageid field (which is a field not to be
> displayed)
> '5678' and '2754' and 10 other dealer numbers (multiple dealer
> numbers).
> How would I know if '5678' is in there as a string value (which is just
> one of the many numbers in that field)? If it has multiple
> dealer numbers separated by commas? Wouldn't the expression for the
> "hidden" value need to be a substring query? How would I do that?
> Thanks,
> Trint
>|||No, it comes from a group within our company that is dedicated only
toward sql server and I am only in c#.net and reporting services.
Trint

can I use the value of field in last record?

I handle a output by a function with three parameters

the first is a value of Field [a1] in current record,

the second is value of Field [a1] in last record,

the third is value of Field [a1] in next record,

is it possible in RS2005?

Yes you can use them in a given scope (table/list):

Fields!a1.Value

Last(Fields!a1.Value, "Dataset1")

Fields!a1.Value(RowNumber("Dataset1")+1)

Shyam

Saturday, February 25, 2012

Can I use a data field returned from my report as part of the URL address?

I am familiar with the navigation hyperlink action of "Jump to URL" but I cant get it to use the data returned in the report as part of the URL address. When I enter the Url into the expression editor: ="http://internal.company.address/sys1/sys2/caseEdit.pl?case="&"Fields!CaseID.Value" it opens an explorer window but it echos the address and tries to use the text 'Fields!CaseID.Value' instead of the data returned in that field.

Can this be done?

="http://internal.company.address/sys1/sys2/caseEdit.pl?case=" & Fields!CaseID.Value

|||Thanks, this answers my question. Seems so simply once I see the answer.

Friday, February 24, 2012

Can I split a field based on a character?

Here's a question for the SQL gurus out there:
I have a varchar(20) field DIAGNOSISCODE in a table that can either be null, or contain up to 3 comma-separated codes, each of which relates to a description in another table. For example, some sample rows might be
8060
8060,4450
8060,4123,3245
Now I need to structure a query to return these values from this single field as three fields CODE1, CODE2, CODE3, with NULL as appropriate for example
CODE1=8060, CODE2=4450, CODE3=NULL.
I have been using CASE along with CHARINDEX and PATINDEX but it it becoming extremely messy. Can anyone think of a "neater" way to return three fields from this one field?
Any help very greatly appreciated.
Thanks, Simon.Here's a question for the SQL gurus out there:
I have a varchar(20) field DIAGNOSISCODE in a table that can either be null, or contain up to 3 comma-separated codes, each of which relates to a description in another table. For example, some sample rows might be
8060
8060,4450
8060,4123,3245
Now I need to structure a query to return these values from this single field as three fields CODE1, CODE2, CODE3, with NULL as appropriate for example
CODE1=8060, CODE2=4450, CODE3=NULL.
I have been using CASE along with CHARINDEX and PATINDEX but it it becoming extremely messy. Can anyone think of a "neater" way to return three fields from this one field?
Any help very greatly appreciated.
Thanks, Simon.

Don't let blindman see this post; he'll pull out the complete works of E.F. Codd!!! :D

Seriously, do a google on fn_Split(). I think you will find it will suit your purposes.

Regards,

hmscott|||check that site,I think that is the best and simple way to do.
http://www.sqlteam.com/item.asp?ItemID=2652|||The requirements are very close to the ones of generating a remittance advice when running Claims Reimbursement...It's been awhile, but I had to deal with the same scenario. First, I stored Dx codes separately from Claim Details. I did have a reference from ClaimDxCodes back to Claim Details table to retain dependency of CPT codes on diagnosis codes (Dx). When printing the Remittance Advice I transformed the data to present it in the format that you're trying to accomplish, using Crystal (the original app was written in VB4 with SQL 6.5). Later, when I recoded the reporting piece for ActiveReports control, I created a sub-report to display the Dx codes as a comma-separated list. But the concept remained the same, - ClaimHeader-->>ClaimDetail-->>ClaimDxCodes. Do not store Dx codes in the same table as your CPT codes, or your claim header info! Doing so violates the fundamentals of relational database principles, and B. Lindman WILL pull out the complete works of Codd at you...Let the massacre begin!..|||That's got me out of a tight spot, thanks very much.
Cheers, Simon.|||I'm really a nice guy. Really.

Sunday, February 19, 2012

Can I sort on fields by in paramters

I need to sort a report in 3 ways 2 fields and one expression.
When i add a field to a parameter it says the following:
"Fields cannot be used in report parameter expressions"
The expression I need to sort on is this
=(sum(Fields!p1beløb.Value) - sum(Fields!p2beløb.Value)) /
(0.001+sum(Fields!p1beløb.Value))
It works if I use this as sort on the group item, but I need to choose
between 3 kinds.
How can I sort the report if I can't use fields to tell how I want it
sorted
?
Jack
--
Jeg beskyttes af den gratis SPAMfighter til privatbrugere.
Den har indtil videre sparet mig for at få 45071 spam-mails.
Betalende brugere får ikke denne besked i deres e-mails.
Hent gratis SPAMfighter her: www.spamfighter.dkCreate a function in the code area which accepts the Parameter ( 1,2 or 3 )
and all of the fields you wish to sort on..
The function should use the parameter in a case/switch statement to choose
which value to return. In one case it should return the value of the
expression you mentioned.
In the sort column pu
=Code.GetSort(Parameters!SortVal.Value,......)
Hope this helps...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jack Nielsen" <no_spam jack.nielsen@.get2net.dk> wrote in message
news:ebEGvm9tFHA.1472@.TK2MSFTNGP15.phx.gbl...
>I need to sort a report in 3 ways 2 fields and one expression.
> When i add a field to a parameter it says the following:
> "Fields cannot be used in report parameter expressions"
> The expression I need to sort on is this
> =(sum(Fields!p1beløb.Value) - sum(Fields!p2beløb.Value)) /
> (0.001+sum(Fields!p1beløb.Value))
> It works if I use this as sort on the group item, but I need to choose
> between 3 kinds.
> How can I sort the report if I can't use fields to tell how I want it
> sorted
> ?
> Jack
>
>
> --
> Jeg beskyttes af den gratis SPAMfighter til privatbrugere.
> Den har indtil videre sparet mig for at få 45071 spam-mails.
> Betalende brugere får ikke denne besked i deres e-mails.
> Hent gratis SPAMfighter her: www.spamfighter.dk
>|||I think this is somehow difficult, doesn't other designers need to sort the
result differently based upon fields ?
Jack
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> skrev i en meddelelse
news:eZbuG$DuFHA.3740@.TK2MSFTNGP14.phx.gbl...
> Create a function in the code area which accepts the Parameter ( 1,2 or
3 )
> and all of the fields you wish to sort on..
> The function should use the parameter in a case/switch statement to choose
> which value to return. In one case it should return the value of the
> expression you mentioned.
> In the sort column pu
> =Code.GetSort(Parameters!SortVal.Value,......)
> Hope this helps...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jack Nielsen" <no_spam jack.nielsen@.get2net.dk> wrote in message
> news:ebEGvm9tFHA.1472@.TK2MSFTNGP15.phx.gbl...
> >I need to sort a report in 3 ways 2 fields and one expression.
> >
> > When i add a field to a parameter it says the following:
> >
> > "Fields cannot be used in report parameter expressions"
> >
> > The expression I need to sort on is this
> > =(sum(Fields!p1beløb.Value) - sum(Fields!p2beløb.Value)) /
> > (0.001+sum(Fields!p1beløb.Value))
> >
> > It works if I use this as sort on the group item, but I need to choose
> > between 3 kinds.
> >
> > How can I sort the report if I can't use fields to tell how I want it
> > sorted
> > ?
> >
> > Jack
> >
> >
> >
> >
> > --
> > Jeg beskyttes af den gratis SPAMfighter til privatbrugere.
> > Den har indtil videre sparet mig for at få 45071 spam-mails.
> > Betalende brugere får ikke denne besked i deres e-mails.
> > Hent gratis SPAMfighter her: www.spamfighter.dk
> >
> >
>

Sunday, February 12, 2012

Can I output the result of sp_spaceused to a table ?

Firstly, I created a table : test01 as follow :
Field Data type
db_name char (80)
db_size char (20)
unallocated_space char (20)
reserved char (20)
data char (20)
index_size char (20)
unused char (20)
Then, I executed this command in SQL Analyzer :
INSERT INTO test01 EXEC sp_spaceused
But I only got this result :
Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
Insert Error: Column name or number of supplied values does not match table
definition
Can I output the result of : EXEC sp_spaceused to a table ?
Was my SQL statement correct or incorrect ?
sp_spaceused has two result sets, so no you can't do that directly...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c8t0tc$91f2@.imsp212.netvigator.com...
> Firstly, I created a table : test01 as follow :
> Field Data type
> db_name char (80)
> db_size char (20)
> unallocated_space char (20)
> reserved char (20)
> data char (20)
> index_size char (20)
> unused char (20)
> Then, I executed this command in SQL Analyzer :
> INSERT INTO test01 EXEC sp_spaceused
> But I only got this result :
> Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
> Insert Error: Column name or number of supplied values does not match
table
> definition
>
> Can I output the result of : EXEC sp_spaceused to a table ?
> Was my SQL statement correct or incorrect ?
>
>
|||Try looking at the code in master..sp_spaceused. You could probably pick
out the portions into separate procs. Would loose the features of new
sp_spaceused during a SQL Server version upgrade but if you are desperate
enough this is an option.
-Paritosh
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:eoF5B4ZQEHA.3744@.TK2MSFTNGP10.phx.gbl...
> sp_spaceused has two result sets, so no you can't do that directly...
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c8t0tc$91f2@.imsp212.netvigator.com...
> table
>
|||> Would loose the features of new
> sp_spaceused during a SQL Server version upgrade but if you are desperate
> enough this is an option.
Right, but to be honest, that is slightly safer than relying on the sp_ to
not change... since if you *could* do insert #table exec sp_spaceused and
the resultset changes, suddenly your code breaks. If your code is merely
*based on* the sp_ then it won't break when the sp_ changes.
Then again, your code would likely rely on calls to system tables such as
sysindexes etc. which are going to change and which will eventually
disappear, so neither method would be truly safe...
A

Can I output the result of sp_spaceused to a table ?

Firstly, I created a table : test01 as follow :
Field Data type
db_name char (80)
db_size char (20)
unallocated_space char (20)
reserved char (20)
data char (20)
index_size char (20)
unused char (20)
Then, I executed this command in SQL Analyzer :
INSERT INTO test01 EXEC sp_spaceused
But I only got this result :
Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
Insert Error: Column name or number of supplied values does not match table
definition
Can I output the result of : EXEC sp_spaceused to a table ?
Was my SQL statement correct or incorrect ?sp_spaceused has two result sets, so no you can't do that directly...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c8t0tc$91f2@.imsp212.netvigator.com...
> Firstly, I created a table : test01 as follow :
> Field Data type
> db_name char (80)
> db_size char (20)
> unallocated_space char (20)
> reserved char (20)
> data char (20)
> index_size char (20)
> unused char (20)
> Then, I executed this command in SQL Analyzer :
> INSERT INTO test01 EXEC sp_spaceused
> But I only got this result :
> Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
> Insert Error: Column name or number of supplied values does not match
table
> definition
>
> Can I output the result of : EXEC sp_spaceused to a table ?
> Was my SQL statement correct or incorrect ?
>
>|||Try looking at the code in master..sp_spaceused. You could probably pick
out the portions into separate procs. Would loose the features of new
sp_spaceused during a SQL Server version upgrade but if you are desperate
enough this is an option.
-Paritosh
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:eoF5B4ZQEHA.3744@.TK2MSFTNGP10.phx.gbl...
> sp_spaceused has two result sets, so no you can't do that directly...
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c8t0tc$91f2@.imsp212.netvigator.com...
> table
>|||> Would loose the features of new
> sp_spaceused during a SQL Server version upgrade but if you are desperate
> enough this is an option.
Right, but to be honest, that is slightly safer than relying on the sp_ to
not change... since if you *could* do insert #table exec sp_spaceused and
the resultset changes, suddenly your code breaks. If your code is merely
*based on* the sp_ then it won't break when the sp_ changes.
Then again, your code would likely rely on calls to system tables such as
sysindexes etc. which are going to change and which will eventually
disappear, so neither method would be truly safe...
A

Can I output the result of sp_spaceused to a table ?

Firstly, I created a table : test01 as follow :
Field Data type
db_name char (80)
db_size char (20)
unallocated_space char (20)
reserved char (20)
data char (20)
index_size char (20)
unused char (20)
Then, I executed this command in SQL Analyzer :
INSERT INTO test01 EXEC sp_spaceused
But I only got this result :
Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
Insert Error: Column name or number of supplied values does not match table
definition
Can I output the result of : EXEC sp_spaceused to a table ?
Was my SQL statement correct or incorrect ?sp_spaceused has two result sets, so no you can't do that directly...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c8t0tc$91f2@.imsp212.netvigator.com...
> Firstly, I created a table : test01 as follow :
> Field Data type
> db_name char (80)
> db_size char (20)
> unallocated_space char (20)
> reserved char (20)
> data char (20)
> index_size char (20)
> unused char (20)
> Then, I executed this command in SQL Analyzer :
> INSERT INTO test01 EXEC sp_spaceused
> But I only got this result :
> Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
> Insert Error: Column name or number of supplied values does not match
table
> definition
>
> Can I output the result of : EXEC sp_spaceused to a table ?
> Was my SQL statement correct or incorrect ?
>
>|||You can do that at a table level:
Example for Northwind Employees table.
Create Table #Temp1
(Tablename CHAR(80),
rows int,
un_space VARCHAR(50),
reserved VARCHAR(50),
data VARCHAR(50),
index_size VARCHAR(50))
GO
Insert into #Temp1
Exec sp_spaceused 'Employees'
GO
Select * from #Temp1
GO
Drop table #Temp1
GO
>--Original Message--
>Firstly, I created a table : test01 as follow :
>Field Data type
>db_name char (80)
>db_size char (20)
>unallocated_space char (20)
>reserved char (20)
>data char (20)
>index_size char (20)
>unused char (20)
>Then, I executed this command in SQL Analyzer :
>INSERT INTO test01 EXEC sp_spaceused
>But I only got this result :
>Server: Msg 213, Level 16, State 7, Procedure
sp_spaceused, Line 142
>Insert Error: Column name or number of supplied values
does not match table
>definition
>
>Can I output the result of : EXEC sp_spaceused to a
table ?
>Was my SQL statement correct or incorrect ?
>
>.
>|||Try looking at the code in master..sp_spaceused. You could probably pick
out the portions into separate procs. Would loose the features of new
sp_spaceused during a SQL Server version upgrade but if you are desperate
enough this is an option.
-Paritosh
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:eoF5B4ZQEHA.3744@.TK2MSFTNGP10.phx.gbl...
> sp_spaceused has two result sets, so no you can't do that directly...
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "cpchan" <cpchaney@.netvigator.com> wrote in message
> news:c8t0tc$91f2@.imsp212.netvigator.com...
> > Firstly, I created a table : test01 as follow :
> >
> > Field Data type
> > db_name char (80)
> > db_size char (20)
> > unallocated_space char (20)
> > reserved char (20)
> > data char (20)
> > index_size char (20)
> > unused char (20)
> >
> > Then, I executed this command in SQL Analyzer :
> >
> > INSERT INTO test01 EXEC sp_spaceused
> >
> > But I only got this result :
> >
> > Server: Msg 213, Level 16, State 7, Procedure sp_spaceused, Line 142
> > Insert Error: Column name or number of supplied values does not match
> table
> > definition
> >
> >
> > Can I output the result of : EXEC sp_spaceused to a table ?
> > Was my SQL statement correct or incorrect ?
> >
> >
> >
>|||> Would loose the features of new
> sp_spaceused during a SQL Server version upgrade but if you are desperate
> enough this is an option.
Right, but to be honest, that is slightly safer than relying on the sp_ to
not change... since if you *could* do insert #table exec sp_spaceused and
the resultset changes, suddenly your code breaks. If your code is merely
*based on* the sp_ then it won't break when the sp_ changes.
Then again, your code would likely rely on calls to system tables such as
sysindexes etc. which are going to change and which will eventually
disappear, so neither method would be truly safe...
A|||Thanks to everybodies.
"Tom" <anonymous@.discussions.microsoft.com> wrote in message
news:115ac01c441a1$917301b0$a001280a@.phx.gbl...
> You can do that at a table level:
> Example for Northwind Employees table.
>
> Create Table #Temp1
> (Tablename CHAR(80),
> rows int,
> un_space VARCHAR(50),
> reserved VARCHAR(50),
> data VARCHAR(50),
> index_size VARCHAR(50))
> GO
> Insert into #Temp1
> Exec sp_spaceused 'Employees'
> GO
> Select * from #Temp1
> GO
> Drop table #Temp1
> GO
>
> >--Original Message--
> >Firstly, I created a table : test01 as follow :
> >
> >Field Data type
> >db_name char (80)
> >db_size char (20)
> >unallocated_space char (20)
> >reserved char (20)
> >data char (20)
> >index_size char (20)
> >unused char (20)
> >
> >Then, I executed this command in SQL Analyzer :
> >
> >INSERT INTO test01 EXEC sp_spaceused
> >
> >But I only got this result :
> >
> >Server: Msg 213, Level 16, State 7, Procedure
> sp_spaceused, Line 142
> >Insert Error: Column name or number of supplied values
> does not match table
> >definition
> >
> >
> >Can I output the result of : EXEC sp_spaceused to a
> table ?
> >Was my SQL statement correct or incorrect ?
> >
> >
> >
> >.
> >