Hello, everyone!

I need some help determining proper values for one field on a report.
I have an inventory of products. Products are packaged and each package has an expiration date.   For my report, I need to include information on expired packages, so I need to select package ID where expiration date is less than today and product count for package is greater than 0, meaning that there's still some products left in that package.

How do I get that expired package's ID #? I tried using the formula field and when I opened up formula editor, I put in something like

{package.id} = {package.id} where {package.product_count} > 0 and {package.exp_date} < DateTimeValue (now)

but this apparently did not work. What would be the correct syntax/approach for determining the ID of an expired package?

Thanks!  

Hm, I guess I was closer than I imagined then. I must have messed something else up then because I get no results when I should clearly have at least 3, looking at raw table data.

OK, I have a formula field called oldPack and it is based on the previous formula with AND instead of WHERE. I go to bind it and in select expert I choose package.id and set it equal to formula: {@oldPack}
I still have no records returned.

I think the problem is that the above formula seems to return boolean, not an actual number for package ID, but I am not sure how to go around it.

What am I doing wrong here? 


Edited by gphreak - 09 Apr 2007 at 10:28pm

I will try this first thing in the morning.

Another kind of question: if I use default parameter values from a table for my parameters, is there a way to make those default values dynamically update themselves? When new values are entered in the table, the drop down list of default parameter values continues to contain only the values selected at the time the report was created. Is there a way to make those updates using the CR designer and not manually programming them all in?

A few design issues: a report user needs to specify start/end date and 1 or 2 field values at runtime. If there is no way to make those updates to default parameter values dynamically, then I guess I will need to program it all. Can those user input customizations at runtime be achieved just through selection formulas or do I need to use ParameterFields instead? Which is better and why?
In this case then, is ReportDocument model better/more suitable than CrystalReportsViewer model?


Thanks again, and I will continue posting questions as they arise.
I apologize for not splitting this up into separate threads but I did not want to open up 3-4 threads all practically at once.


Edited by gphreak - 09 Apr 2007 at 11:38pm

Thanks for the info. I looked at the following this tutorial http://msdn2.microsoft.com/en-us/library/ms227697(VS.80).aspx and it seems like even though I would have controls to input parameters, it would still have the same issue of not updating itself. Am I mistaken here? The only other way around it that I can think of would be to not specify default values at design time, but do it all from the code, populating the listbox of values through a query and then passing the selected values to the report. Would this work? It may sound like it would but I am not sure.   

Right, right... that's the way it's gonna be then. In that case, I still need to define the parameter field at design time, but I would not be setting any values for it, right?
This way then I can have multiple parameters being specified and passed at runtime. So if I want the user to specify start date and end date as well as choose from default values for some other parameter, it should be no problem? Or is there a limitation of some sort as to how many parameters can be specified and passed at runtime?