Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Time Calculation

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Time Calculation

    Good Morning,

    I could swear I've read my question here once before, but damned if I can find it.

    I've created a table to keep track of the time I spend on my application. I do most of my work at night when I get off of work. So generally I start before 12:00 AM and work past 12:00 AM. This is where my question lies. I want one of my fields,"Totaltime", to calculate the duration between "INTIME" and "OUTTIME".

    I've tried :
    TOTIME(TOSECONDS(OUTTIME)-TOSECONDS(INTIME),1,2 )

    This obviously will not work alone due to the times being to different days. I'm sure someone else has run into this. Enlighten me.

    Brian

    #2
    RE: Time Calculation

    Brian,

    From your posting, I presume that INTIME and OUTTIME are character strings in the format "hh:mm". Regardless, one solution is to make them type T instead. Type T variables contain the date as well as the time to handle such situations as yours. Moreover, to log in or out merely requires that you assign a variable the value NOW() which returns type T.

    Suppose we have:
    ?intime
    = 01/04/2005 10:06:22 29 pm
    ?outtime
    = 01/05/2005 03:06:22 29 am

    Two ways to view time elapsed are:
    ?(outtime-intime)/60 'minutes elapsed
    = 300.000000
    and
    ?totime(outtime-intime,1,0) '(hh:mm)
    = "5:00"

    My 2 minutes,
    Steve

    Comment


      #3
      RE: Time Calculation

      Thanks Steve,

      How would you handle the situation if "INDATE" ,"INTIME" ,"OUTDATE","OUTTIME" were all fields not variables. I'm trying to define the calculation in field rules.

      Thanks Brian

      Comment


        #4
        RE: Time Calculation

        Hi Brian,
        Couldn't you have another field to create the field rule calculation in? Then, when you enter the OUTTIME, your total time would calculate. If you don't want to enter a new record for each time you need to track your time, just edit the one existing record and recalc field rules.

        I've not worked with time fields, but it seems like this would work.

        Wanda

        Comment


          #5
          RE: Time Calculation

          Brian,

          My first inclination was to make these fields type T but after investigating I see that it doesn't seem possible. One solution still appears to be to create type T variables which make use of your fields. This, of course, requires parsing of the various elements of your field values.

          Before proceding, we must first know the types for your fields. Are INDATE and OUTDATE type D? Are INTIME and OUTTIME type C (with an "hh:mm am" format)? I will assume so for the moment.
          Code:
          indate = {01/04/05}
          intime = "10:50 pm"
          outdate = {01/05/05}
          outtime = "02:30 am"
          
          starttime=scantime(dtoc(indate)+" "+intime,"MM/dd/yyyy 0h:0m am")
          ?starttime
          = 01/04/2005 10:50:00 00 pm
          
          endtime=scantime(dtoc(outdate)+" "+outtime,"MM/dd/yyyy 0h:0m am")
          ?endtime
          = 01/05/2005 02:30:00 00 am
          
          ?(endtime - starttime)/60
          = 220.000000
          ?totime(endtime-starttime,1,0)
          = "3:40"
          The above makes use of two variables which could be used within a layout. But I take it that you want a single expression so that you can assign it to another field. If so, these can be combined as follows:
          Code:
          ?(scantime(dtoc(outdate)+" "+outtime,"MM/dd/yyyy 0h:0m am") - scantime(dtoc(indate)+" "+intime,"MM/dd/yyyy 0h:0m am"))/60
          = 220.000000
          I hope this helps.

          Steve

          Comment


            #6
            RE: Time Calculation

            Brian,

            This is from a message posted some time ago by Russ Boehle...

            These are entered as field rules.
            Time_in, Time_Out, Date_In and Date_Out are the fields in question here:

            elapsed time:
            totime(toseconds(Time_Out)-toseconds(Time_In)+((Date_Out-Date_In)*3600*24),1,0)

            decimal elapsed time:
            round((toseconds(Time_Out)-toseconds(Time_In)+((Date_Out-Date_In)*3600*24))/3600,2)

            HTH

            Charles
            SwissCharles
            Between the Alps and a comfy place

            Comment


              #7
              RE: Time Calculation

              Hello,

              Thank you all for your help

              Brian

              Comment

              Working...
              X