Hi,
I am looking for a query to extract hour and AM or PM value from a date on sql2000.
ex/-
Input : 2001-12-28 22:18:07.810 (from getdate())
Output : 10 PM
select convert(varchar, (datepart(hh, convert(varchar, getdate(), 8)) % 12)) + ' ' +
substring (convert(varchar, convert(datetime, getdate(),20), 100),
DATALENGTH(convert(varchar, convert(datetime, getdate(),20), 100)) - 1,
DATALENGTH(convert(varchar, convert(datetime, getdate(),20), 100 )))
The above works but is there a better way to do this?This is a little shorter:
SELECT CONVERT(VARCHAR,DATEPART(hh,GETDATE())%12) +
CASE WHEN (DATEPART(hh,GETDATE())%12) > 0 THEN ' PM' ELSE ' AM' END|||thanks for your reply.
but i figured that 12 AM or 12 PM was displayed as 0 AM and 0 PM.
Hence to reduce my troubles, i will stick with the good ol' substring.
SELECT (substring(CONVERT(VARCHAR,getdate(),22),10,2) + ' ' +
substring(CONVERT(VARCHAR,getdate(),22), 19,2))
Showing posts with label output. Show all posts
Showing posts with label output. Show all posts
Thursday, March 29, 2012
Monday, March 26, 2012
External columns vs. output columns?
Can someone please explain the difference between Output and External columns? I can't fathom why "Output" columns aren't good enough. In other words, what is there a need or value in having two types of "output" columns?
TIA,
Barkingdong
Does this help: http://blogs.conchango.com/jamiethomson/archive/2006/05/23/3984.aspx ?
-Jamie
|||External columns help to make a snapshot of the external metadata. It is used as reference for future changes in the external source and internal metadata (output columns).
For example, let's say we do not have external columns and at certain point of time you have 2 output columns in the collection and 3 columns in the linked external table (or flat file, etc). That does not give us enough information to determine if we ignored one column at the source or the table was updated with an additional column.
With external columns we have a reference to compare against, and that allows automatic updates of changed metadata, through the ReinitializeMetadata mechanism, without disrupting the downstream components.
HTH.
|||Your answers (including Jamie's too) surprised me. But I need to slow you down a bit (that's the problem with experts, you know) to better understand your answer. Here are some of my thoughts. Please comment on any portion, in any manner, you wish.
1. So "external" columns relate to metadata used at design time to verify, among other things, that the source and destination mappings are in "sync" or appropriate.
2. I don't remember much discussion of metadata in sql 2000 DTS. Was it there but hidden, did I simply miss it, or is this a sql 2005 enhancement?
3. "...External columns help to make a snapshot of the external metadata. "
Suppose I have a Flat File Source Connector and an OLE DB Destination connector. What does "external" refer to here in SSIS talk? Are the "external columns" metadata references from the Flat File connector that refer to the inputs of the "external" OLE DB Destination connector?
4.I found this BOL reference:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/8f5bd3ed-3e79-43a4-b6c1-435e4c2cc8cc.htm
"
When a component is disconnected from its data source, you can validate the columns in the input and output column collections against the columns at its external data source by using the IDTSExternalMetadataColumnCollection90 interface. This interface lets you maintain a snapshot of the columns at the external data source and map these columns to the columns in the input and output column collection of the component.
Implementing external metadata columns adds a layer of overhead and complexity to component development, because you must maintain and validate against an additional column collection, but the ability to avoid expensive round trips to the server for validation may make this development work worthwhile.
"
That is interesting. Disconnected, ahh...
While I can drag and drop input/output fields between tasks, I gather that I wouldn't normally adjust (unless I was programming in .NET) external\internal metadata columns. In a sense I shouldn't be too concerned with metadata on a daily basis. It's part of the SSIS infrastructure but something that I generally won't touch.
TIA,
Barkingdog
|||barkingdog wrote:
Your answers (including Jamie's too) surprised me. But I need to slow you down a bit (that's the problem with experts, you know) to better understand your answer. Here are some of my thoughts. Please comment on any portion, in any manner, you wish.
1. So "external" columns relate to metadata used at design time to verify, among other things, that the source and destination mappings are in "sync" or appropriate.
Yeah, that's a good way of looking at it!
2. I don't remember much discussion of metadata in sql 2000 DTS. Was it there but hidden, did I simply miss it, or is this a sql 2005 enhancement?
Very much a sql 2005 thing.
3. "...External columns help to make a snapshot of the external metadata. "
Suppose I have a Flat File Source Connector and an OLE DB Destination connector. What does "external" refer to here in SSIS talk? Are the "external columns" metadata references from the Flat File connector that refer to the inputs of the "external" OLE DB Destination connector?
Nothing as sinister as that. Its quite simply the metadata of the thing that SSIS is going to connect to.
4.I found this BOL reference:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/8f5bd3ed-3e79-43a4-b6c1-435e4c2cc8cc.htm
"
When a component is disconnected from its data source, you can validate the columns in the input and output column collections against the columns at its external data source by using the IDTSExternalMetadataColumnCollection90 interface. This interface lets you maintain a snapshot of the columns at the external data source and map these columns to the columns in the input and output column collection of the component.
Implementing external metadata columns adds a layer of overhead and complexity to component development, because you must maintain and validate against an additional column collection, but the ability to avoid expensive round trips to the server for validation may make this development work worthwhile.
"
That is interesting. Disconnected, ahh...
While I can drag and drop input/output fields between tasks, I gather that I wouldn't normally adjust (unless I was programming in .NET) external\internal metadata columns. In a sense I shouldn't be too concerned with metadata on a daily basis. It's part of the SSIS infrastructure but something that I generally won't touch.
That's a safe bet. Let SSIS do the grunt for you - you just use what it gives you!!
-Jamie
Friday, March 23, 2012
Extensive Use pf Case Statement
Hi,
I want to generate a table output as per table a based on table b. In this case Range field os populated based on Shape and Process field values. You can see in both processes range is different. Now this is varies from shapes & processes which is stored in seperate master table which contains range ex. For Process_1 it is 0.5 & for Process_2 it is 0.10.
I have tried used case statement but I am unable to generate this dynamically in a single query. Can anyone Help me How can I achive this task?
Table A
Table B
Nilkanth Desai
create table TableB(Barcode int, Shape char(6), Process varchar(8), Weight decimal(5,2))
insert into TableB(Barcode ,Shape , Process ,Weight)
select 1 , 'Shap_1', 'Proc_1' , 0.12 union all
select 2 , 'Shap_1', 'Proc_1' , 0.16 union all
select 3 , 'Shap_1', 'Proc_1' , 0.06 union all
select 4 , 'Shap_1', 'Proc_1' , 0.21 union all
select 5 , 'Shap_1', 'Proc_1' , 0.13 union all
select 6 , 'Shap_1', 'Proc_2' , 0.18 union all
select 7 , 'Shap_1', 'Proc_2' , 0.13 union all
select 8 , 'Shap_1', 'Proc_2', 0.24 union all
select 9 , 'Shap_1', 'Proc_2', 0.07 union all
select 10 , 'Shap_1', 'Proc_2', 0.33
create table Master(Process varchar(8), Range decimal(5,2))
insert into Master(Process, Range) values('Proc_1',0.05)
insert into Master(Process, Range) values('Proc_2',0.10)
select t.Barcode,
t.Shape,
t.Process,
t.Weight,
floor(t.Weight/m.Range)*m.Range+0.01 as RangeFrom,
floor(t.Weight/m.Range)*m.Range+m.Range as RangeTo
from TableB t
inner join Master m on m.Process=t.Process
order by t.Barcode
Monday, March 19, 2012
Extended Stored Procedure
I have written extend stored procedure using dblib.
declare @.p1 int
xp_myProc 'select * from table', @.p1 output.
This extended procedure exeute the query and generate the
xml. Using xp_prepardocument it generate the handle.
The output handle i want to use it another procedure to
read the value.
<anonymous@.discussions.microsoft.com> wrote in message
news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
>I have written extend stored procedure using dblib.
> declare @.p1 int
> xp_myProc 'select * from table', @.p1 output.
> This extended procedure exeute the query and generate the
> xml. Using xp_prepardocument it generate the handle.
> The output handle i want to use it another procedure to
> read the value.
Are you having problems with the handle no longer being valid?
Bryant
|||Note that the handle is valid for the duration of a session. If your xp runs
in a different session context, the handle cannot be reused...
Best regards
Michael
"Bryant Likes" <bryant@.suespammers.org> wrote in message
news:%23mDquOsdEHA.712@.TK2MSFTNGP09.phx.gbl...
> <anonymous@.discussions.microsoft.com> wrote in message
> news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
> Are you having problems with the handle no longer being valid?
> --
> Bryant
>
declare @.p1 int
xp_myProc 'select * from table', @.p1 output.
This extended procedure exeute the query and generate the
xml. Using xp_prepardocument it generate the handle.
The output handle i want to use it another procedure to
read the value.
<anonymous@.discussions.microsoft.com> wrote in message
news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
>I have written extend stored procedure using dblib.
> declare @.p1 int
> xp_myProc 'select * from table', @.p1 output.
> This extended procedure exeute the query and generate the
> xml. Using xp_prepardocument it generate the handle.
> The output handle i want to use it another procedure to
> read the value.
Are you having problems with the handle no longer being valid?
Bryant
|||Note that the handle is valid for the duration of a session. If your xp runs
in a different session context, the handle cannot be reused...
Best regards
Michael
"Bryant Likes" <bryant@.suespammers.org> wrote in message
news:%23mDquOsdEHA.712@.TK2MSFTNGP09.phx.gbl...
> <anonymous@.discussions.microsoft.com> wrote in message
> news:717501c47625$ef3aeb60$a401280a@.phx.gbl...
> Are you having problems with the handle no longer being valid?
> --
> Bryant
>
Friday, March 9, 2012
expression in Visibility>Hidden field = No output to csv
Hi all,
I have a problem with a report I have created. It has around 52 columns and each column is shown or hidden based on a boolean parameter. Simple huh? I though so.
I have a problem with a report I have created. It has around 52 columns and each column is shown or hidden based on a boolean parameter. Simple huh? I though so.
Each column has an expression similar to =IIF(Parameters!showfirstname.Value,False,True) for the Hidden field. This is not the hidden field for the 'cell' or 'header' but for the entire column.
The problem is, the report is correctly displayed as a pdf, tiff, excel file (possibly others), but all columns with an expression as the hidden value are not displayed in the xml or csv output regardless of the parameter value. This also applies if the expression is =IIF(True,False,True) or =IIF(1=1,False,True).
As soon as I change this field back to a simple 'True' or 'False' it displays correctly. I've tried playing around with setting the output options to values other than the default Auto setting to no avail.
There are numerous comments about this on newsgroups online going back to the first release of reporting services but none of them have solutions.
Regards
John Burns
John,
You can't conditionally hide and show data in data renderers (CSV, XML). This is by design. If you have an expression in the Hidden field and 'Auto' in DataOutput tab for text boxes in the column, your data will not be rendered into CSV or XML.
You can set DataElementOutput to Output for textboxes in the cells and in the header, and the coulmn will always be in the output file.
Thanks!
|||
You could in SQL 2000!
I've just upgraded to 2005 and exports to csv format no longer work whereas they did in SQL 2000. I've tracked the culpit down to the visibility statement. If there is an expression
e.g.
=IIf(1=1, false, true)
against the table then the data will render in all formats except csv\xml. This is a breaking change that has been introduced in 2005 so I would expect that microsoft would consider fixing it or producing a hot fix for affected systems. Note that I haven't applied any service packs but haven't seen anything related to this issue in the SP's.
Try this example report which queries sysobjects in the master database (change the data source first)
<?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">
<DataSources>
<DataSource Name="DataSource1">
<ConnectionProperties>
<IntegratedSecurity>true</IntegratedSecurity>
<ConnectString>Data Source=SQLServer;Initial Catalog=master</ConnectString>
<DataProvider>SQL</DataProvider>
</ConnectionProperties>
<rd:DataSourceID>145254b5-d42f-46f6-a007-7898e2fb93b4</rd:DataSourceID>
</DataSource>
</DataSources>
<BottomMargin>2.5cm</BottomMargin>
<RightMargin>2.5cm</RightMargin>
<PageWidth>21cm</PageWidth>
<rd:DrawGrid>true</rd:DrawGrid>
<InteractiveWidth>8.5in</InteractiveWidth>
<rd:GridSpacing>0.25cm</rd:GridSpacing>
<rd:SnapToGrid>true</rd:SnapToGrid>
<Body>
<ColumnSpacing>1cm</ColumnSpacing>
<ReportItems>
<Textbox Name="textbox1">
<rd:DefaultName>textbox1</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Report1</Value>
</Textbox>
<Table Name="table1">
<DataSetName>DataSource1</DataSetName>
<Top>0.91429cm</Top>
<Visibility>
<Hidden>=IIf(1=1, false, true)</Hidden>
</Visibility>
<Width>5.07936cm</Width>
<Details>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="name">
<DataElementOutput>Output</DataElementOutput>
<rd:DefaultName>name</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!name.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="id">
<DataElementOutput>Output</DataElementOutput>
<rd:DefaultName>id</rd:DefaultName>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!id.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.53333cm</Height>
</TableRow>
</TableRows>
</Details>
<Header>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox2">
<rd:DefaultName>textbox2</rd:DefaultName>
<ZIndex>3</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>name</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox3">
<rd:DefaultName>textbox3</rd:DefaultName>
<ZIndex>2</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<TextAlign>Right</TextAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>id</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.55873cm</Height>
</TableRow>
</TableRows>
<RepeatOnNewPage>true</RepeatOnNewPage>
</Header>
<TableColumns>
<TableColumn>
<Width>2.53968cm</Width>
</TableColumn>
<TableColumn>
<Width>2.53968cm</Width>
</TableColumn>
</TableColumns>
</Table>
</ReportItems>
<Height>2.00635cm</Height>
</Body>
<rd:ReportID>10fa5646-bbb8-452c-b281-7f6cb1fc3a6c</rd:ReportID>
<LeftMargin>2.5cm</LeftMargin>
<DataSets>
<DataSet Name="DataSource1">
<Query>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
<CommandText>select * from sysobjects</CommandText>
<DataSourceName>DataSource1</DataSourceName>
</Query>
<Fields>
<Field Name="name">
<rd:TypeName>System.String</rd:TypeName>
<DataField>name</DataField>
</Field>
<Field Name="id">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>id</DataField>
</Field>
<Field Name="xtype">
<rd:TypeName>System.String</rd:TypeName>
<DataField>xtype</DataField>
</Field>
<Field Name="uid">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>uid</DataField>
</Field>
<Field Name="info">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>info</DataField>
</Field>
<Field Name="status">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>status</DataField>
</Field>
<Field Name="base_schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>base_schema_ver</DataField>
</Field>
<Field Name="replinfo">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>replinfo</DataField>
</Field>
<Field Name="parent_obj">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>parent_obj</DataField>
</Field>
<Field Name="crdate">
<rd:TypeName>System.DateTime</rd:TypeName>
<DataField>crdate</DataField>
</Field>
<Field Name="ftcatid">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>ftcatid</DataField>
</Field>
<Field Name="schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>schema_ver</DataField>
</Field>
<Field Name="stats_schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>stats_schema_ver</DataField>
</Field>
<Field Name="type">
<rd:TypeName>System.String</rd:TypeName>
<DataField>type</DataField>
</Field>
<Field Name="userstat">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>userstat</DataField>
</Field>
<Field Name="sysstat">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>sysstat</DataField>
</Field>
<Field Name="indexdel">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>indexdel</DataField>
</Field>
<Field Name="refdate">
<rd:TypeName>System.DateTime</rd:TypeName>
<DataField>refdate</DataField>
</Field>
<Field Name="version">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>version</DataField>
</Field>
<Field Name="deltrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>deltrig</DataField>
</Field>
<Field Name="instrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>instrig</DataField>
</Field>
<Field Name="updtrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>updtrig</DataField>
</Field>
<Field Name="seltrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>seltrig</DataField>
</Field>
<Field Name="category">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>category</DataField>
</Field>
<Field Name="cache">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>cache</DataField>
</Field>
</Fields>
</DataSet>
</DataSets>
<Width>12.69841cm</Width>
<InteractiveHeight>11in</InteractiveHeight>
<Language>en-US</Language>
<TopMargin>2.5cm</TopMargin>
<PageHeight>29.7cm</PageHeight>
</Report>
expression in Visibility>Hidden field = No output to csv
Hi all,
I have a problem with a report I have created. It has around 52 columns and each column is shown or hidden based on a boolean parameter. Simple huh? I though so.
I have a problem with a report I have created. It has around 52 columns and each column is shown or hidden based on a boolean parameter. Simple huh? I though so.
Each column has an expression similar to =IIF(Parameters!showfirstname.Value,False,True) for the Hidden field. This is not the hidden field for the 'cell' or 'header' but for the entire column.
The problem is, the report is correctly displayed as a pdf, tiff, excel file (possibly others), but all columns with an expression as the hidden value are not displayed in the xml or csv output regardless of the parameter value. This also applies if the expression is =IIF(True,False,True) or =IIF(1=1,False,True).
As soon as I change this field back to a simple 'True' or 'False' it displays correctly. I've tried playing around with setting the output options to values other than the default Auto setting to no avail.
There are numerous comments about this on newsgroups online going back to the first release of reporting services but none of them have solutions.
Regards
John Burns
John,
You can't conditionally hide and show data in data renderers (CSV, XML). This is by design. If you have an expression in the Hidden field and 'Auto' in DataOutput tab for text boxes in the column, your data will not be rendered into CSV or XML.
You can set DataElementOutput to Output for textboxes in the cells and in the header, and the coulmn will always be in the output file.
Thanks!
|||
You could in SQL 2000!
I've just upgraded to 2005 and exports to csv format no longer work whereas they did in SQL 2000. I've tracked the culpit down to the visibility statement. If there is an expression
e.g.
=IIf(1=1, false, true)
against the table then the data will render in all formats except csv\xml. This is a breaking change that has been introduced in 2005 so I would expect that microsoft would consider fixing it or producing a hot fix for affected systems. Note that I haven't applied any service packs but haven't seen anything related to this issue in the SP's.
Try this example report which queries sysobjects in the master database (change the data source first)
<?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">
<DataSources>
<DataSource Name="DataSource1">
<ConnectionProperties>
<IntegratedSecurity>true</IntegratedSecurity>
<ConnectString>Data Source=SQLServer;Initial Catalog=master</ConnectString>
<DataProvider>SQL</DataProvider>
</ConnectionProperties>
<rd:DataSourceID>145254b5-d42f-46f6-a007-7898e2fb93b4</rd:DataSourceID>
</DataSource>
</DataSources>
<BottomMargin>2.5cm</BottomMargin>
<RightMargin>2.5cm</RightMargin>
<PageWidth>21cm</PageWidth>
<rd:DrawGrid>true</rd:DrawGrid>
<InteractiveWidth>8.5in</InteractiveWidth>
<rd:GridSpacing>0.25cm</rd:GridSpacing>
<rd:SnapToGrid>true</rd:SnapToGrid>
<Body>
<ColumnSpacing>1cm</ColumnSpacing>
<ReportItems>
<Textbox Name="textbox1">
<rd:DefaultName>textbox1</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Report1</Value>
</Textbox>
<Table Name="table1">
<DataSetName>DataSource1</DataSetName>
<Top>0.91429cm</Top>
<Visibility>
<Hidden>=IIf(1=1, false, true)</Hidden>
</Visibility>
<Width>5.07936cm</Width>
<Details>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="name">
<DataElementOutput>Output</DataElementOutput>
<rd:DefaultName>name</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!name.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="id">
<DataElementOutput>Output</DataElementOutput>
<rd:DefaultName>id</rd:DefaultName>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!id.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.53333cm</Height>
</TableRow>
</TableRows>
</Details>
<Header>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox2">
<rd:DefaultName>textbox2</rd:DefaultName>
<ZIndex>3</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>name</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox3">
<rd:DefaultName>textbox3</rd:DefaultName>
<ZIndex>2</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<TextAlign>Right</TextAlign>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>id</Value>
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.55873cm</Height>
</TableRow>
</TableRows>
<RepeatOnNewPage>true</RepeatOnNewPage>
</Header>
<TableColumns>
<TableColumn>
<Width>2.53968cm</Width>
</TableColumn>
<TableColumn>
<Width>2.53968cm</Width>
</TableColumn>
</TableColumns>
</Table>
</ReportItems>
<Height>2.00635cm</Height>
</Body>
<rd:ReportID>10fa5646-bbb8-452c-b281-7f6cb1fc3a6c</rd:ReportID>
<LeftMargin>2.5cm</LeftMargin>
<DataSets>
<DataSet Name="DataSource1">
<Query>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
<CommandText>select * from sysobjects</CommandText>
<DataSourceName>DataSource1</DataSourceName>
</Query>
<Fields>
<Field Name="name">
<rd:TypeName>System.String</rd:TypeName>
<DataField>name</DataField>
</Field>
<Field Name="id">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>id</DataField>
</Field>
<Field Name="xtype">
<rd:TypeName>System.String</rd:TypeName>
<DataField>xtype</DataField>
</Field>
<Field Name="uid">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>uid</DataField>
</Field>
<Field Name="info">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>info</DataField>
</Field>
<Field Name="status">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>status</DataField>
</Field>
<Field Name="base_schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>base_schema_ver</DataField>
</Field>
<Field Name="replinfo">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>replinfo</DataField>
</Field>
<Field Name="parent_obj">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>parent_obj</DataField>
</Field>
<Field Name="crdate">
<rd:TypeName>System.DateTime</rd:TypeName>
<DataField>crdate</DataField>
</Field>
<Field Name="ftcatid">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>ftcatid</DataField>
</Field>
<Field Name="schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>schema_ver</DataField>
</Field>
<Field Name="stats_schema_ver">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>stats_schema_ver</DataField>
</Field>
<Field Name="type">
<rd:TypeName>System.String</rd:TypeName>
<DataField>type</DataField>
</Field>
<Field Name="userstat">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>userstat</DataField>
</Field>
<Field Name="sysstat">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>sysstat</DataField>
</Field>
<Field Name="indexdel">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>indexdel</DataField>
</Field>
<Field Name="refdate">
<rd:TypeName>System.DateTime</rd:TypeName>
<DataField>refdate</DataField>
</Field>
<Field Name="version">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>version</DataField>
</Field>
<Field Name="deltrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>deltrig</DataField>
</Field>
<Field Name="instrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>instrig</DataField>
</Field>
<Field Name="updtrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>updtrig</DataField>
</Field>
<Field Name="seltrig">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>seltrig</DataField>
</Field>
<Field Name="category">
<rd:TypeName>System.Int32</rd:TypeName>
<DataField>category</DataField>
</Field>
<Field Name="cache">
<rd:TypeName>System.Int16</rd:TypeName>
<DataField>cache</DataField>
</Field>
</Fields>
</DataSet>
</DataSets>
<Width>12.69841cm</Width>
<InteractiveHeight>11in</InteractiveHeight>
<Language>en-US</Language>
<TopMargin>2.5cm</TopMargin>
<PageHeight>29.7cm</PageHeight>
</Report>
Subscribe to:
Posts (Atom)