A report VIEWER control ! How about the report DESIGNER control ?

Hi all, our team is really excited about the new ReportViewer control.
Heck, it even supports custom data sources, which fits in nicely with our
overall application design.
The only thing that seems to be missing then is a control that allows our
users to design (or at least modify) reports themselves. In our mind,
the biggest advantage to working with a report engine and report files
is the ability to provide your users with customizable reports.
Moreover, we know this functionality exists since we (programmers)
use the report designer in VS2005. So it would be up to Microsoft to
package it into a control and ship it.
I'm sure somebody else has already asked about this by now but repeated
google queries have turned up nothing relevant.
Thanks for any light anyone can shed on this.
Sven
PS: I hope my cross-posting does notTake a look at the information about Report Builder in Reporting
Services 2005. That is intended to give end users the ability to
design their own reports.
But it's not a control though. Of course, until recently the Report
Viewer control didn't exist either. :)
Andrew Watt
MVP - InfoPath
On Wed, 12 Oct 2005 12:19:45 +0200, "Sven Devriese"
<desfen@.newsgroup.nospam> wrote:
>Hi all, our team is really excited about the new ReportViewer control.
>Heck, it even supports custom data sources, which fits in nicely with our
>overall application design.
>The only thing that seems to be missing then is a control that allows our
>users to design (or at least modify) reports themselves. In our mind,
>the biggest advantage to working with a report engine and report files
>is the ability to provide your users with customizable reports.
>Moreover, we know this functionality exists since we (programmers)
>use the report designer in VS2005. So it would be up to Microsoft to
>package it into a control and ship it.
>I'm sure somebody else has already asked about this by now but repeated
>google queries have turned up nothing relevant.
>Thanks for any light anyone can shed on this.
>Sven
>PS: I hope my cross-posting does not
>|||It is not as simple as that. The report designer is built to work with
Visual Studio and takes advantage of common functionality (for instance, all
the query design windows). As a matter of fact, the designer in 2005 now
ships with a special version of VS 2005. Plus you also have vb.net etc etc.
For that reason I don't expect to ever see this as a redistributable.
However, as Andrew mentioned, there is now Report Builder as well for end
users.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sven Devriese" <desfen@.newsgroup.nospam> wrote in message
news:usVb5ZxzFHA.612@.TK2MSFTNGP10.phx.gbl...
> Hi all, our team is really excited about the new ReportViewer control.
> Heck, it even supports custom data sources, which fits in nicely with our
> overall application design.
> The only thing that seems to be missing then is a control that allows our
> users to design (or at least modify) reports themselves. In our mind,
> the biggest advantage to working with a report engine and report files
> is the ability to provide your users with customizable reports.
> Moreover, we know this functionality exists since we (programmers)
> use the report designer in VS2005. So it would be up to Microsoft to
> package it into a control and ship it.
> I'm sure somebody else has already asked about this by now but repeated
> google queries have turned up nothing relevant.
> Thanks for any light anyone can shed on this.
> Sven
> PS: I hope my cross-posting does not
>|||Keep in mind that Report Builder generated RDL files cannot be used directly
with the report viewer controls in Local Mode. They can however be easily
used with the controls in Server Mode.
RDL is a documented and open standard, e.g. for the 2003/10 RDL of RS 2000
please check http://www.microsoft.com/sql/reporting/techinfo/rdlspec.mspx,
the 2005/01 RDL is very similar. You could write your own designer component
that generates RDL. In fact, there are ISVs who have implemented e.g.
web-based report authoring tools. Please check:
http://www.microsoft.com/sql/reporting/partners/default.mspx
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Watt [MVP - InfoPath]" <SVGDeveloper@.aol.com> wrote in message
news:g8upk1tmjfb3vasb96s71r36aadm4lohks@.4ax.com...
> Take a look at the information about Report Builder in Reporting
> Services 2005. That is intended to give end users the ability to
> design their own reports.
> But it's not a control though. Of course, until recently the Report
> Viewer control didn't exist either. :)
> Andrew Watt
> MVP - InfoPath
> On Wed, 12 Oct 2005 12:19:45 +0200, "Sven Devriese"
> <desfen@.newsgroup.nospam> wrote:
>>Hi all, our team is really excited about the new ReportViewer control.
>>Heck, it even supports custom data sources, which fits in nicely with our
>>overall application design.
>>The only thing that seems to be missing then is a control that allows our
>>users to design (or at least modify) reports themselves. In our mind,
>>the biggest advantage to working with a report engine and report files
>>is the ability to provide your users with customizable reports.
>>Moreover, we know this functionality exists since we (programmers)
>>use the report designer in VS2005. So it would be up to Microsoft to
>>package it into a control and ship it.
>>I'm sure somebody else has already asked about this by now but repeated
>>google queries have turned up nothing relevant.
>>Thanks for any light anyone can shed on this.
>>Sven
>>PS: I hope my cross-posting does not
>

a player team tables design?

i am a beginner of database design, could anyone please help me to
figure out how to make these two tables work.

1) a "players" table, with columns "name", "age"
2) a "teams" table, which can have one OR two player(s)
a team also has a column "level", which may have values "A", "B",
or "C"

how do you build the "teams" table (the critical question is "do i
need to create two fields" for the maximum two possible players?")

how do you use one query to display the information with the following
columns:
"name", "age", "levelA", "levelB", "levelC" (the later three columns
are integer type, showing how many teams with coresponding level this
player is in).

now suppose i don't have any access to sql server, i save the data
into xml, and load it into a dataset. how could you do the selection
within the dataset? or ahead of that, how do you specify the relations
between "players" and "teams".

the following is the schema file i am trying to make (I still don't
know if i need to specified the primary key... and how to build
relation between them):
<code>
<?xml version="1.0" ?>
<xs:schema id="AllTables" xmlns=""
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="AllTables" msdata:IsDataSet="true">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="Players">
<xs:complexType>
<xs:sequence>
<xs:element name="PlayerID" msdata:AutoIncrement="true"
type="xs:int" minOccurs="0" />
<xs:element name="Name" type="xs:string" minOccurs="0" />
<xs:element name="Age" type="xs:int" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Teams">
<xs:complexType>
<xs:sequence>
<xs:element name="TeamID" msdata:AutoIncrement="true"
type="xs:int" minOccurs="0" />
<xs:element name="Level" type="xs:string" minOccurs="0" />
<xs:element name="Player1" type="xs:int" minOccurs="0" />
<xs:element name="Player2" type="xs:int" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
</code>In SQL it might be something like this to start with. Start reading about
normalization, relational theory, and table driven applications.

CREATE TABLE Team
( TeamId INTEGER NOT NULL PRIMARY KEY
, TeamName VARCHAR(40) NOT NULL
, TeamLevel CHAR(1) NOT NULL CHECK (TeamLevel IN ('A', 'B', 'C'))
)

CREATE TABLE Player
( PlayerId INTEGER NOT NULL PRIMARY KEY
, PlayerName VARCHAR(40) NOT NULL
, TeamId INTEGER NOT NULL FOREIGN KEY REFERENCES Team(TeamId)
)

"Alan Zhong" <alanchinese@.yahoo.com> wrote in message
news:b09c98a8.0408260048.79651f10@.posting.google.c om...
>i am a beginner of database design, could anyone please help me to
> figure out how to make these two tables work.
> 1) a "players" table, with columns "name", "age"
> 2) a "teams" table, which can have one OR two player(s)
> a team also has a column "level", which may have values "A", "B",
> or "C"
> how do you build the "teams" table (the critical question is "do i
> need to create two fields" for the maximum two possible players?")
> how do you use one query to display the information with the following
> columns:
> "name", "age", "levelA", "levelB", "levelC" (the later three columns
> are integer type, showing how many teams with coresponding level this
> player is in).
> now suppose i don't have any access to sql server, i save the data
> into xml, and load it into a dataset. how could you do the selection
> within the dataset? or ahead of that, how do you specify the relations
> between "players" and "teams".
>
> the following is the schema file i am trying to make (I still don't
> know if i need to specified the primary key... and how to build
> relation between them):
> <code>
> <?xml version="1.0" ?>
> <xs:schema id="AllTables" xmlns=""
> xmlns:xs="http://www.w3.org/2001/XMLSchema"
> xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
> <xs:element name="AllTables" msdata:IsDataSet="true">
> <xs:complexType>
> <xs:choice maxOccurs="unbounded">
> <xs:element name="Players">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="PlayerID" msdata:AutoIncrement="true"
> type="xs:int" minOccurs="0" />
> <xs:element name="Name" type="xs:string" minOccurs="0" />
> <xs:element name="Age" type="xs:int" minOccurs="0" />
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> <xs:element name="Teams">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="TeamID" msdata:AutoIncrement="true"
> type="xs:int" minOccurs="0" />
> <xs:element name="Level" type="xs:string" minOccurs="0" />
> <xs:element name="Player1" type="xs:int" minOccurs="0" />
> <xs:element name="Player2" type="xs:int" minOccurs="0" />
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:choice>
> </xs:complexType>
> </xs:element>
> </xs:schema>
> </code|||And this would be one way to express the query that you're looking for.
Feel free to add age to schema and query.

SELECT PlayerName
, (SELECT COUNT(*) FROM Team WHERE TeamId = Player.TeamId AND TeamLevel =
'A') As LevelA
, (SELECT COUNT(*) FROM Team WHERE TeamId = Player.TeamId AND TeamLevel =
'B') As LevelB
, (SELECT COUNT(*) FROM Team WHERE TeamId = Player.TeamId AND TeamLevel =
'C') As LevelC
FROM Player

"Larry S" <nospam@.bugus.zzz> wrote in message
news:M17Yc.107934$TI1.103116@.attbi_s52...
> In SQL it might be something like this to start with. Start reading about
> normalization, relational theory, and table driven applications.
> CREATE TABLE Team
> ( TeamId INTEGER NOT NULL PRIMARY KEY
> , TeamName VARCHAR(40) NOT NULL
> , TeamLevel CHAR(1) NOT NULL CHECK (TeamLevel IN ('A', 'B', 'C'))
> )
> CREATE TABLE Player
> ( PlayerId INTEGER NOT NULL PRIMARY KEY
> , PlayerName VARCHAR(40) NOT NULL
> , TeamId INTEGER NOT NULL FOREIGN KEY REFERENCES Team(TeamId)
> )
> "Alan Zhong" <alanchinese@.yahoo.com> wrote in message
> news:b09c98a8.0408260048.79651f10@.posting.google.c om...
>>i am a beginner of database design, could anyone please help me to
>> figure out how to make these two tables work.
>>
>> 1) a "players" table, with columns "name", "age"
>> 2) a "teams" table, which can have one OR two player(s)
>> a team also has a column "level", which may have values "A", "B",
>> or "C"
>>
>> how do you build the "teams" table (the critical question is "do i
>> need to create two fields" for the maximum two possible players?")
>>
>> how do you use one query to display the information with the following
>> columns:
>> "name", "age", "levelA", "levelB", "levelC" (the later three columns
>> are integer type, showing how many teams with coresponding level this
>> player is in).
>>
>> now suppose i don't have any access to sql server, i save the data
>> into xml, and load it into a dataset. how could you do the selection
>> within the dataset? or ahead of that, how do you specify the relations
>> between "players" and "teams".
>>
>>
>> the following is the schema file i am trying to make (I still don't
>> know if i need to specified the primary key... and how to build
>> relation between them):
>> <code>
>> <?xml version="1.0" ?>
>> <xs:schema id="AllTables" xmlns=""
>> xmlns:xs="http://www.w3.org/2001/XMLSchema"
>> xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
>> <xs:element name="AllTables" msdata:IsDataSet="true">
>> <xs:complexType>
>> <xs:choice maxOccurs="unbounded">
>> <xs:element name="Players">
>> <xs:complexType>
>> <xs:sequence>
>> <xs:element name="PlayerID" msdata:AutoIncrement="true"
>> type="xs:int" minOccurs="0" />
>> <xs:element name="Name" type="xs:string" minOccurs="0" />
>> <xs:element name="Age" type="xs:int" minOccurs="0" />
>> </xs:sequence>
>> </xs:complexType>
>> </xs:element>
>> <xs:element name="Teams">
>> <xs:complexType>
>> <xs:sequence>
>> <xs:element name="TeamID" msdata:AutoIncrement="true"
>> type="xs:int" minOccurs="0" />
>> <xs:element name="Level" type="xs:string" minOccurs="0" />
>> <xs:element name="Player1" type="xs:int" minOccurs="0" />
>> <xs:element name="Player2" type="xs:int" minOccurs="0" />
>> </xs:sequence>
>> </xs:complexType>
>> </xs:element>
>> </xs:choice>
>> </xs:complexType>
>> </xs:element>
>> </xs:schema>
>> </code>