I don't see any way to do this short of using a script to place the data you want in a text field. Then your text field can be referenced in your tool tip. The problem you then have to solve is when to run the script so that the tool tip displays correct results from this field.
Ok - thanks.
Just because I don't see a way doesn't mean that it can't be done :smileywink:
You never know what some other clever developer might come up with.
I suppose I could add a "Days" table, and have one record for every day of the year, then have a relationship that is the date = the date from the Daily Sales table, and then have the tooltip looking up a field that sums the daily sales records from within the Days table.
Would that work do you think?
Then I'd just have to automate adding in a record for every day of every year.
Hmm, I wonder if you'll encounter a significant performance penalty when your layout refreshes and all these tool tips recalculate....
I have a simple technique in one of my databases for creating a log of business days (days we are open for business instead of all the days in the year.).
Every time a cashier prints an invoice, the print script includes this step:
Set Field [DayCount:: Date; Invoice:: DatePrinted]
The relationship between DayCount and Invoice is configured to allow creation of related records in DayCount.
When the first invoice is printed each day, this relationship creates a new record.
All subsequent runs of the invoice print script simply set the existing record to the value it already contains and this leaves me with one business day record logged each time we print at least one invoice for the day.
Yes, adding this complexity for the sake of some tooltips may well add more overheads that slow it down too much. There are a lot of calculation fields already on this layout, as the user wants to see the sales (and various other figures based on the sales) for the quarter across the page in a horizontal fashion.
I'll see. I tried playing around with creating a value list for the dates, and then using the "ValueListItems" function to list each unique date, and this worked, but I can't do the same thing for the SUM field of the sales data, as it can't be stored.