Fast running sum or a way to index times.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • arnegrant
    New Member
    • Jan 2010
    • 4

    Fast running sum or a way to index times.

    I have a table with the following

    Autonumber Time Temp
    1 01:00:10 500
    2 02:01:10 600
    3 02:00:15 650
    .
    .
    .
    .
    11,759 23:59:00 700
    11,760 23:59:10 600
    11,761 23:59:50 650
    11,762 00:00:10 750
    11.763 00:05:50 800
    .
    .
    .
    .
    .
    23,759 23:59:10 700
    23,760 23:59:15 700
    23,761 23:59:55 760
    23,762 00:00:15 900
    23,763 00:06:50 800
    .
    .
    .
    .
    Etcetera....

    My issue is I need to graph the time on the X coordinate and the temperature on the Y coordinate (easy) but the clock resets every 24 hours and the logs run for days.

    The time is not equal, the records are not equal, I need the x coordinates to be scaled and the times vary so I cannot graph by the log number, and I have no control over the software writing it.

    I have created a running sum using Dsum, but it takes too long (it is for a multiuser application that will be used many times on many different changing data sets)

    I'm out of ideas, any help would be appreciated.

    Thank you.
  • nico5038
    Recognized Expert Specialist
    • Nov 2006
    • 3080

    #2
    As you have an autoumber, the sequence is already fixed, what's the problem in using the Graph control on this data ?

    Nic;o)

    Comment

    • arnegrant
      New Member
      • Jan 2010
      • 4

      #3
      I am doing a scatter plot and it needs to scale based on the time value so I can't use the sequence number.

      After some doing I was able to contact the software writer and have them alter the log time to run continuous and not reset to 0 at 24 hours.

      After I had the time consistant I was able to do my scatter plots.

      Thanks for the help, Arne

      Comment

      • Stewart Ross
        Recognized Expert Moderator Specialist
        • Feb 2008
        • 2545

        #4
        Hi. I'm glad you have resolved this one, but just in case it may help in other ways, please note that if the developers had provided you with the date along with the time you would have had the data you needed without further alteration of their log times. Maybe this is what has been done when you mention they have altered their log times not to reset each day.

        Given separate log date and time values, even if these are just output as text, you could have converted them to true date/time values using Access or Excel to do so. In all the Office applications, a time value is just an instance of a date/time value, just as a date is an instance of a date/time value. They are aspects of the same data type, and can be shown separately or together by using formatting options to present the value in whatever way is required.

        In MS Office, Date/Time values are stored as decimal values where the whole-number component represents the date (internally stored as a count of the number of days passed from a date of about 1 January 1900), and the decimal component represents the time (with 0.5 representing 12 mid-day, 0.75 being 1800 hours, and so on).

        A date and time value generated from a data logger at set times of the day will simply increase linearly over time - by 1 for the passage of a day, by 0.5 for the passage of half a day, and so on. It is a scalar value that you can plot in whatever charting application you are using for your x/y plot.

        -Stewart

        Comment

        Working...