Adding A Multivalue Parameter

I've got a simple report built that retrieves data based on a serial
number assign to each record. The user has to type the serial number
into the box to run the report. Now I would like to add another
parameter in which they can run the report based on either a date/time
stamp (Start - End) and/or a multivalue parameter from another field
in each record. Do I need to create a new dataset to add these
features to the report ? I've tried adding the multivalue parameter
but either get an error or the drop down is empty.
Thank-you
JeffOn Feb 5, 4:04 pm, jsvi...@.gmail.com wrote:
> I've got a simple report built that retrieves data based on a serial
> number assign to each record. The user has to type the serial number
> into the box to run the report. Now I would like to add another
> parameter in which they can run the report based on either a date/time
> stamp (Start - End) and/or a multivalue parameter from another field
> in each record. Do I need to create a new dataset to add these
> features to the report ? I've tried adding the multivalue parameter
> but either get an error or the drop down is empty.
> Thank-you
> Jeff
If the original dataset is based on a serial number parameter/etc that
always has a value/default value, you should be ok. Of course, you
will want to have this multivalue parameter as the second parameter in
the list (behind the parameter it is dependent on). If this does not
work, then you might want to try adding an additional dataset as you
mentioned. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Feb 5, 8:41=A0pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Feb 5, 4:04 pm, jsvi...@.gmail.com wrote:
> > I've got a simple report built that retrieves data based on a serial
> > number assign to each record. The user has to type the serial number
> > into the box to run the report. Now I would like to add another
> > parameter in which they can run the report based on either a date/time
> > stamp (Start - End) and/or a multivalue parameter from another field
> > in each record. Do I need to create a new dataset to add these
> > features to the report ? I've tried adding the multivalue parameter
> > but either get an error or the drop down is empty.
> > Thank-you
> > Jeff
> If the original dataset is based on a serial number parameter/etc that
> always has a value/default value, you should be ok. Of course, you
> will want to have this multivalue parameter as the second parameter in
> the list (behind the parameter it is dependent on). If this does not
> work, then you might want to try adding an additional dataset as you
> mentioned. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
I would like to be able to use each parameter independently or
together if possible. Here is the report query that I started with:
SELECT SpindleName AS Tool, Timestamp AS [Date-Time], Accept,
FinalAngle AS Angle, PartId AS CSN, CycleStatus AS Status, PeakTorque
AS Torque
FROM Readings
WHERE (PartId =3D @.PartId)
ORDER BY CSN DESC
The user types the CSN number in a gets a report showing the data for
every tool. I'd like to allow them to run the report based on
selecting one or more specific tools with or without a dependancy on
the CSN number. Is this possible ?
Thanks
Jeff

Add a second databse - benefits?

Hi, there is an existing application running on a SQL Server database.

Now I have to built a different app, which will have two common tables
with the existing database (Customers, sales)

Is there any benefit (performance mainly) creating the tables for the
new app in a new database? (On the same machine and the same instance)

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!chora (choracy@.hotmail.com) writes:
> Hi, there is an existing application running on a SQL Server database.
> Now I have to built a different app, which will have two common tables
> with the existing database (Customers, sales)
> Is there any benefit (performance mainly) creating the tables for the
> new app in a new database? (On the same machine and the same instance)

There is too little information to say anything with certainty. If the
two apps not only share the table definitions, but also the data in
the table, putting everything in the same database.

As long as the applications are access their individual tables, there
is not much interferance between them. All I can think is that autogrow
caused by one app will affect the userss of the other app two, but
autogrows should not occur frequently.

Of course, in the common tables there may be blocking issues with
improper application design.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||
Erland ,

thanks for the reply.

The databases will share the data of the two tables. The new database
will have 'read only' access to these tables.

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Hi

If these tables are large, then you may want to make them federated and
create a partitioned view for them. This may give you a performance
improvement e.g http://vyaskn.tripod.com/federated.htm

There may also be other reasons to use a separate database such as ownership
(e.g if a third party package it may invalidate the waranty to stick extra
tables in there), security and maintainance.

John

"chora" <choracy@.hotmail.com> wrote in message
news:40d5962f$0$16472$c397aba@.news.newsgroups.ws.. .
>
> Hi, there is an existing application running on a SQL Server database.
> Now I have to built a different app, which will have two common tables
> with the existing database (Customers, sales)
> Is there any benefit (performance mainly) creating the tables for the
> new app in a new database? (On the same machine and the same instance)
>
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!