> I am sure that these are FAQs, but I can not find them listed anywhere and
> they are certainly not answered in my copy of the 8.5 user's guide.  Any
> help woudl be appreciated:

> 1. Is there a way to have the options for a parameter list pulled from a
> data source rather than have them be hard-coded?  (Any tricks like using
> subreports ect...?)

> 2. Is there any way of having an "ALL" selection added to your list of
> parameter values and have that set as the default value?

> GOAL: Develop a report that has multiple parameters whose choices should
be
> made froma a distinct lookup of certain fields and allow the user to
specify
> "ALL" on some or all of the parameters.  (EG: Have the user choose
"Status",
> "State" and "Type" where Status is a list of all distinct values of
statuus
> found in a "Status" filed *plus* the default choice of "All" which would
> indicate that the report should not select based upon status at all.  Do
the
> same for the State and Type fields.)

> Thanks again for any help that is available!

> Answering the second question first:  Yes, you can offer that choice.  I
use
> CR7 and have done this.  I specify my choices when I create the parameter
> field, the first one in the list being my default value.  In my record
> selection formula, I have an If..Then statement like:  If ?Status <> "ALL"
> Then {Table.Status} = ?Status Else True
> You will probably have one of these clauses for each parameter.

> For the first question:  We use Crystal Enterprise for our users to access
> their reports.  I don't remember all of the details, but, we have created
> picklist reports that, when processed, create text files which are lists
of
> all of the choices that we want to offer to a user.  Our regular reports
use
> the picklist text file for the parameter list, rather than hard coding the
> list.  Even this method requires that the picklist report be processed
> regularly, or at least right before a standard report, so that the list is
> kept up to date.

> I'm certain that there must be better ways of doing this, but it satisfies
> our needs right now.

> Bob Holmes

> > I am sure that these are FAQs, but I can not find them listed anywhere
and
> > they are certainly not answered in my copy of the 8.5 user's guide.  Any
> > help woudl be appreciated:

> > 1. Is there a way to have the options for a parameter list pulled from a
> > data source rather than have them be hard-coded?  (Any tricks like using
> > subreports ect...?)

> > 2. Is there any way of having an "ALL" selection added to your list of
> > parameter values and have that set as the default value?

> > GOAL: Develop a report that has multiple parameters whose choices should
> be
> > made froma a distinct lookup of certain fields and allow the user to
> specify
> > "ALL" on some or all of the parameters.  (EG: Have the user choose
> "Status",
> > "State" and "Type" where Status is a list of all distinct values of
> statuus
> > found in a "Status" filed *plus* the default choice of "All" which would
> > indicate that the report should not select based upon status at all.  Do
> the
> > same for the State and Type fields.)

> > Thanks again for any help that is available!

> Thank you for your help!  I appreciate you taking the time to give me such
> an answer.

> If anyone else has info on the dreaded "I want a dynamically generated
> picklist parameter" problem, please let us know!

> > Answering the second question first:  Yes, you can offer that choice.  I
> use
> > CR7 and have done this.  I specify my choices when I create the
parameter
> > field, the first one in the list being my default value.  In my record
> > selection formula, I have an If..Then statement like:  If ?Status <>
"ALL"
> > Then {Table.Status} = ?Status Else True
> > You will probably have one of these clauses for each parameter.

> > For the first question:  We use Crystal Enterprise for our users to
access
> > their reports.  I don't remember all of the details, but, we have
created
> > picklist reports that, when processed, create text files which are lists
> of
> > all of the choices that we want to offer to a user.  Our regular reports
> use
> > the picklist text file for the parameter list, rather than hard coding
the
> > list.  Even this method requires that the picklist report be processed
> > regularly, or at least right before a standard report, so that the list
is
> > kept up to date.

> > I'm certain that there must be better ways of doing this, but it
satisfies
> > our needs right now.

> > Bob Holmes

> > > I am sure that these are FAQs, but I can not find them listed anywhere
> and
> > > they are certainly not answered in my copy of the 8.5 user's guide.
Any
> > > help woudl be appreciated:

> > > 1. Is there a way to have the options for a parameter list pulled from
a
> > > data source rather than have them be hard-coded?  (Any tricks like
using
> > > subreports ect...?)

> > > 2. Is there any way of having an "ALL" selection added to your list of
> > > parameter values and have that set as the default value?

> > > GOAL: Develop a report that has multiple parameters whose choices
should
> > be
> > > made froma a distinct lookup of certain fields and allow the user to
> > specify
> > > "ALL" on some or all of the parameters.  (EG: Have the user choose
> > "Status",
> > > "State" and "Type" where Status is a list of all distinct values of
> > statuus
> > > found in a "Status" filed *plus* the default choice of "All" which
would
> > > indicate that the report should not select based upon status at all.
Do
> > the
> > > same for the State and Type fields.)

> > > Thanks again for any help that is available!

> I checked with my co-worker about the picklist.  We used one report to
> create the picklist for others by having the picklist report provide its
> output as a text file.  Our other reports import the picklist within their
> parameter's properties.  If you are using a front-end, you could write
some
> code to update the picklist file before your reports get processed.  We
got
> our information from a knowledgebase article at Crystal Decisions.

> Bob Holmes

> > Thank you for your help!  I appreciate you taking the time to give me
such
> > an answer.

> > If anyone else has info on the dreaded "I want a dynamically generated
> > picklist parameter" problem, please let us know!

> > > Answering the second question first:  Yes, you can offer that choice.
I
> > use
> > > CR7 and have done this.  I specify my choices when I create the
> parameter
> > > field, the first one in the list being my default value.  In my record
> > > selection formula, I have an If..Then statement like:  If ?Status <>
> "ALL"
> > > Then {Table.Status} = ?Status Else True
> > > You will probably have one of these clauses for each parameter.

> > > For the first question:  We use Crystal Enterprise for our users to
> access
> > > their reports.  I don't remember all of the details, but, we have
> created
> > > picklist reports that, when processed, create text files which are
lists
> > of
> > > all of the choices that we want to offer to a user.  Our regular
reports
> > use
> > > the picklist text file for the parameter list, rather than hard coding
> the
> > > list.  Even this method requires that the picklist report be processed
> > > regularly, or at least right before a standard report, so that the
list
> is
> > > kept up to date.

> > > I'm certain that there must be better ways of doing this, but it
> satisfies
> > > our needs right now.

> > > Bob Holmes

> > > > I am sure that these are FAQs, but I can not find them listed
anywhere
> > and
> > > > they are certainly not answered in my copy of the 8.5 user's guide.
> Any
> > > > help woudl be appreciated:

> > > > 1. Is there a way to have the options for a parameter list pulled
from
> a
> > > > data source rather than have them be hard-coded?  (Any tricks like
> using
> > > > subreports ect...?)

> > > > 2. Is there any way of having an "ALL" selection added to your list
of
> > > > parameter values and have that set as the default value?

> > > > GOAL: Develop a report that has multiple parameters whose choices
> should
> > > be
> > > > made froma a distinct lookup of certain fields and allow the user to
> > > specify
> > > > "ALL" on some or all of the parameters.  (EG: Have the user choose
> > > "Status",
> > > > "State" and "Type" where Status is a list of all distinct values of
> > > statuus
> > > > found in a "Status" filed *plus* the default choice of "All" which
> would
> > > > indicate that the report should not select based upon status at all.
> Do
> > > the
> > > > same for the State and Type fields.)

> > > > Thanks again for any help that is available!