Originally Posted by
rpeare
Item I and II:
I'm using a formatting property of colc to get just the date with no timestamp. If you go to the query design and click the COLC row for the 'current' set of data then click properties in your query design window you can see it says 'short date' you can remove that formatting property and it will show the full date/time. The data is sorted by the full date/time not just the date part of the field.
Item III
Running sums and sums are different things, running sums in queries is generally a bad idea, you can do it using domain functions (DSUM in this case) but it's a very bad idea. Let's say your dataset has 1000 rows, every time you use a domain function your query is evaluating the result based on all 1000 rows, in this case it's the worst possible scenario in that you are showing each row as a unique record and if you had 1 dsum calculation for each row you would effectively square the number of records the database has to process to give you your results (1000 initial records x 1000 records processed in a domain function for each row or 1,000,000 records to process). Your spreadsheet has 2 running sum columns which would double this to 2,000,000 possible calculations.
However, if you perform your running sums on a report, the reports are built for the running sum calculation and will be a hell of a lot quicker.