Selection Range vs. Individual Selection Parameters

[2ffat]

In CR 8.5, selection parameters allow you to have a range. For example, if I want to select data based between two dates I have two options: 1) I can create two selection parameters, a starting date and an ending date; or 2) I can create one parameter and use a range. Both seem to work OK.

My question is which is better and why. James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that they think I am now
qualified to do anything with nothing.

 

[kcorrigan]

James,
In my opinion, one is not necessarily better than the other. I guess it would depend on how you plan to run the report. The range gives you the option of choosing "no upper bound" or "no lower bound" if you don't want to limit the report to a specific begin and/or end date. But as far as run time, I personally haven't seen any difference in the performance of the report based on the type of date parameter set up.

Kristi

 

[dgillz]

If you use a date range parameter, you cannot enter a ending date prior to the begining date, whereas if there were 2 parameters the user could make this type of mistake when executing the report. Software Support for Macola, Crystal Reports and Goldmine
dgilsdorf@mchsi.com

 

[rosemaryl]

Dear 2FFat,

Another issue is that Range Parameters are not supported when reports are viewed over the web! (I personally like Range Parameters best and use them whenever a report will not be run from web - I fnd them easier to reference and also for the reaons Dgillz and KCorrigan stated.

ro Rosemary Lieberman
rosemary@microflo.com,

http://www.microflo.com

Microflo provides expert consulting on MagicTSD and Crystal Reports.

 

[synapsevampire]

Range Parameters work in CE 8.5, which is the WEB.

Either of them *can* be passed in SQL, so given that performance is the same, I'm not sure what other advantages weigh heavily.

Most users grasp the single point of entry for both halves of the date range *parameter* more readily with a range because it will display both simultaneously (using Active-X).

There are a couple of options on ranges which are great, but can be ambiguous (something like include upper range and sumpin else, forgive me, I don't have Crystal here...)

I'd vote for the range value, unless there's some bug involved as Ro mentioned.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[kcorrigan]

To my knowledge, range parameters do not work when running a Crystal Report in a web application. Synapsevampire, do you have code to prove this? I'd be interested in seeing it.

 

[synapsevampire]

I think that range parameters work fine in Crystal Enterprise 8.5, and I don't recall problems in 8.0.

But then, I don't use URL passing, which might be what Ro is referencing. Though you can pass a range using ASP with the RDC.

ref:

http://support.crystaldecisions.com/library/kbase/articles/c2007345.asp

I have multiple reports using them, at least I think that they're using them...

<jumping onto Enterprise to re-check>

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[kcorrigan]

Thanks for the info. I knew the lower & upper bounds would not work in ASP (which I am NOT thrilled about because our users liked this option in VB), but I did not know that the range would still work. Thanks again!

 

[lyanch]

As far as the SQL goes. Crystal handles a range parameter just like one >= and one <=.

If you are using stored procedures, you can't use range paramters (Crystal won't allow you to assign one paramter to another either).

Range parameters don't work well through asp or csp.

Although on range parameters you can state &quot;no upper&quot; or &quot;no lower&quot; bound, you can also easily account for this in code as well.

So basically, it depends on your users. If they really WANT to enter both at the same time then I would try to use it. I personally never use them as too many of my reports are web accessed and I can check the &quot;valid range&quot; easily within my code.

Lisa

 

[kcorrigan]

We have several reports that they use now (in VB) where they're looking up orders & some need to see orders within a date range and others only want to see begin date and all orders past that date (which would be no upper bound). I'm sure they'll be upset if I don't try to get this option added into the web-based program I'm setting up.