Jan 4, 2000, 11:21 AM
Post #2 of 9
If you create a separate data file that gets updated every time a ticket is completed, you have your extremely fast solution.
For example, the data file can contain:
Within the actual ticket data, you have a start time (and date). When the ticket is closed, you can a completion time. With this information, get the total time for the ticket and update your total time data file.
Personally, (unless you use Julian or other date formats) I would keep the year, month, and day as separate fields in your total time data file for searching options... this would allow for more customizable queries (eg January 15, 2000 through August 19, 2000) without needing to split the date each time (which can itself take a while on really large data files).
If any of the above is confusing, please reply and we'll be glad to clarify.