In another thread, Erika wrote:
Quote:use ">|@Date - 30|" .... It will also run faster than your programmed retrieve spec.
Hi Erika!
I remember you mentioning this at the conference, and I made a note that it was important to me, but I've forgotten just how and in what instances Piping should be used. Can you explain its use in a bit more detail?
Is it just for date calculations? Should I place pipes around all my date manipulations (and by all I mean form programming as well as report programming)? Would it serve any purpose in a programming calculation such as:
Invoice_Age = @ToNumber(@Date) - @ToNumber(Invoice_Date)
or a report calculation such as:
Var MonthTotal as Double
MonthTotal = @ToMoney(@XLookup("MonthTotals.db", @Year(@Date) - 1, "Year", @Month$(@Date)))
Last_Year = "Last year's total for " + @Month$(@Date) + " was: $" + @STR(MonthTotal)
Or is it just for retrieve specs? Here's one I use to retrieve this month's invoices:
{@Year(Invoice_Date) = @Year(@Date) AND @Month(Invoice_Date) = @Month(@Date)}
How would piping be used on that? Is it as simple as replacing the curly braces?
Thanks!