Dynamic AI Support Forum

Using List Options | Filters
I have a report working successfully with the default value of = @max(), but how do I specify a different range like '@max()-9' to '@max()' to get the last 10 days?

You can't use an expression as a filter default so you will have to write an expression in "free conditions" on the condition tab page.

In case you're using a Dynamic SQL view -- and haven't tried out @Param# -- you might also want to explore how you can also add your own where clause to the view using a paramter, set a default value and then prompt the user at runtime for a value.

Regards,
Bob

Bob, maybe if I state the goal.

[strike]...........[/strike]

solved it, never mind

BTW... I think our mutual friend Fern mentioned to me that you're using P.SQL as the backend.
If that's right -- and your data dates back to the early days of DAW's Btrieve driver, then you have blank date values. SQL doesn't understand that -- and you'll find rows becoming invisible in many date selection scenarios. The only way I figured out around this was to use a combinatino of the Cast and Coalesce functions like this:

cast(coalesce(job.shipped,'1753-01-01') as date) as job_Shipped.

Coalesce returns a blank value as the string '1753-01-01' or an actual date value as a string. Cast then converts that string back to a date data type.

Also did you know you can create a System Parameter to display all those ugly "zero" dates as blanks in Dynamic AI output? -- i.e. '01/01/1900' or in my example '01/01/1753' would display as blank:
Key = Application
KeyName = ZERODATE
KeyType = DATE
DisplayVal = yyyy-mm-dd (i.e. whatever your zero date value is such as 1753-01-01 or 1900-01-01 - no quotes around the value)

Cheers,
Bob

Bob Cergol wrote:BTW... I think our mutual friend Fern mentioned to me that you're using P.SQL as the backend......
Bob

No, I have two sites (albeit they'll be one network very soon) and this one is MSSQL, but thanks for the tip. Once this one is sold in then I'll start trying to convert the head office too.

In the longer term (12 months?) I think we'll be MSSQL throughout. Pity, and Novell/PSQL has been a fantastic servant for 20 years+, but I can't bring in Novell/Btrieve knowledge in anyone under 40.

I'm way over 40!

Back when I was selling an ERP type of system my 1st choice of backend was Btrieve. It was fast, incredibly sturdy and required no attention.

However -- it was the Btrieve -- so called "navigational engine" that I think we both loved, not their pasted-on so-called relational engine -- Scaleable SQL, then P.SQL -- but hey -- I think you're talking about the days before Novell became Unix!