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

military time

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

    military time

    Hi Phorum,

    Does anyone know a simple way to convert military time to conventional
    time? Ex: convert 1030 to 10:30 AM. I will be deeply indebted to
    anyone with a solution.

    Thanks in advance,
    efs

    #2
    RE: military time

    Ed,

    I always thought military time was:

    15:30:00 (I think this is the time format alpha Five uses)

    If so, conversion to am or pm depends on whether or not the first two digits are equal to or greater than 12. If you subtract 12 from the first two digits and the answer is zero or less, it's am, otherwise it's pm.


    01:30:00 would be 1:30 am
    13:30:00 would be 1:30 pm

    -- tom

    Comment


      #3
      RE: military time

      Hi Tom,

      Thank you for responding so quickly. My client uses 1030 for 10:30 AM,
      and 2030 for 8:30 PM, I could strip it apart and add the colon. I was
      hoping there is a simpler approach.

      efs

      Comment


        #4
        RE: military time

        why don't you define a mask in field rules so the characters are added automatically?

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: military time

          Bill,

          WHile that's a good idea, won't the : only appear as a "mask"? It don't think it inserts the : as part of the field's value which would be needed for conversion?

          kenn
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment


            #6
            RE: military time

            Hi William,

            Gud thawt, I'll give it a try.
            efs

            Comment


              #7
              RE: military time

              Depends on whether you check the box to store mask literals. In other words, it's your choice.

              Bill
              Bill Hanigsberg

              Comment


                #8
                RE: military time

                Edward,

                Long ago when I used to use a flatfile database called Q&A, the would allow time to be entered in numerous ways, including 15.30 format, which would be military time for 3:30 PM. Doing time calculations in there was a snap. However, Alpha Four would not allow that. So, I picked up an idea somewhere provided by someone I do not recall that was a bit more detailed in programming the field rules, but offered a simpler data entry. Two fields for IN time and two for OUT time.

                INHOUR
                INMIN
                OUTHOUR
                OUTMIN

                Each Numeric, length of 2, 0 decimals

                If I want to enter 7:00 AM I enter 07 in the inhour field. After entering 07 the cursor automatically moves to INMIN and I proceed to enter 00. So it's real quick data entry. I then enter the stop time in the OUTHR and OUTMIN fields. I might enter a 3:30 PM stop time, which would be 15 and 30. So as fast as you can type 07001530, the cursor movement is done automatically, and after I enter the final 0 the cursor leaves the field OUTMIN and all the time calculations are done immediately.

                When I print this info in reports I make a calculated display that combines INHOUR, INMIN, OUTHR, and OUTMIN to display as 07:00 and 15:30. I'm sure it wouldn't be too hard to turn the above into 7:00 AM and 3:30 PM.

                Please let me know if you have any questions. I'd be more than happy to supply the programming I use if it would help you in any way.

                Thanks,
                Mike
                Thank you,
                Mike Konoff

                Comment


                  #9
                  RE: military time

                  Ed,

                  Mask to automatically have the ":" inserted, then use the following

                  totime(toseconds("fieldname-10:30"),11,0) = 10:30 am

                  Hope this does it.

                  Tom

                  Comment


                    #10
                    RE: military time

                    Thank you all for your input. I put a mask on the time input field
                    and that is working OK.

                    Thank you all again,
                    efs

                    Comment


                      #11
                      RE: military time

                      Well, learned something that I never gave any thought to previously. I always thought that it meant it would be stored or visible for viewing all the time, not just when the field has focus. Now, I understand the jist of it. And to that I say, "Oh Dah!"

                      Thanks, Bill.

                      kenn
                      TYVM :) kenn

                      Knowing what you can achieve will not become reality until you imagine and explore.

                      Comment

                      Working...
                      X