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

Age in SQL calculation help

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

  • Age in SQL calculation help

    I'm trying to get an accurate age calculation. The way I have it now seems to only calculate the year.

    If I enter 7-13-2014 as the date of birth I get age 59 ...correct.

    If I enter 7-15-2014 (which is tomorrow as I type this) the age remains 59 and it should be 58

    Here is the calculation I am currently using

    (datediff(day,[DOB],getdate())/(365))

    What is the correct calculation??





    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant

  • #2
    Re: Age in SQL calculation help

    are you defining this in your mssql table?
    why not just the date of birth and calculate wherever you want, let alpha do the job for you

    (datediff(day,[DOB],getdate())/(365))
    is not accurate, does not consider leap years.
    thanks for reading

    gandhi

    version 11 3381 - 4096
    mysql backend
    http://www.alphawebprogramming.blogspot.com
    [email protected]
    Skype:[email protected]
    1 914 924 5171

    Comment


    • #3
      Re: Age in SQL calculation help

      It's a computed column in my SQL 2012 table. The table was made long ago by someone else and changing to an Alpha based calculation may break something else. I need an accurate calculation within SQL.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant

      Comment


      • #4
        Re: Age in SQL calculation help

        Mike try this FLOOR(DATEDIFF(day,DOB,GETDATE())/365.242199)

        Comment


        • #5
          Re: Age in SQL calculation help

          Originally posted by bea2701 View Post
          Mike try this FLOOR(DATEDIFF(day,DOB,GETDATE())/365.242199)
          That brought the accuracy to within two weeks! ....The Age will change to '58' if I make the DOB 7/29/1955
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant

          Comment


          • #6
            Re: Age in SQL calculation help

            Try using this as your calculation formula:

            CASE WHEN (MONTH(GETDATE())*100)+DAY(GETDATE()) >= (MONTH(DOB)*100)+DAY(DOB) THEN DATEDIFF(Year,DOB,GETDATE()) ELSE DATEDIFF(Year,DOB,GETDATE())-1 END
            Brad Weaver, President
            ComputerAid International
            Ottawa ON Canada
            Versailles KY USA
            www.compuaid.com

            Comment


            • #7
              Re: Age in SQL calculation help

              Originally posted by compuaid View Post
              Try using this as your calculation formula:

              CASE WHEN (MONTH(GETDATE())*100)+DAY(GETDATE()) >= (MONTH(DOB)*100)+DAY(DOB) THEN DATEDIFF(Year,DOB,GETDATE()) ELSE DATEDIFF(Year,DOB,GETDATE())-1 END
              I think we have a winner! ...thanks!
              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant

              Comment


              • #8
                Re: Age in SQL calculation help

                Anyone care to explain why these hoops must be jumped?

                Is it because the birthday hasn't occurred yet in the second case?

                Comment


                • #9
                  Re: Age in SQL calculation help

                  I am still not sure why age has to stored in the table, whatever application that will be looking at the data can easily calculate the age and will be perfect since it will be updated constantly.
                  I for one will not store a calculated value in the table unless it refers to a fixed data in a changing world.
                  for example retail selling price discounted for what ever the reason, the selling price, even calculated, I will store it.
                  age on the other hand is not a value that needs to be stored in a table, in my opinion.
                  thanks for reading

                  gandhi

                  version 11 3381 - 4096
                  mysql backend
                  http://www.alphawebprogramming.blogspot.com
                  [email protected]
                  Skype:[email protected]
                  1 914 924 5171

                  Comment


                  • #10
                    Re: Age in SQL calculation help

                    The beauty of calculated fields in SQL Server are that they are not physically stored in the table (unless you choose the PERSIST option when you create the field which is necessary if you want to build an index on the field). By using a calculated field in the table you make the current age available to any report, form, stored procedure etc without having to make a SQL function call or re-write the calculation routine in every client app that might have need of this information. This is especially helpful with business logic as it places the logic at the record level and eliminates redundancy and chance of erroneous data being submitted. While having the AGE field calculate on the fly may not be a necessity, in the case of this particular instance Mike stated that he was dealing with a legacy system where other clients were relying on the data which was proving to be inaccurate.
                    Brad Weaver, President
                    ComputerAid International
                    Ottawa ON Canada
                    Versailles KY USA
                    www.compuaid.com

                    Comment


                    • #11
                      Re: Age in SQL calculation help

                      Originally posted by bea2701 View Post
                      Mike try this FLOOR(DATEDIFF(day,DOB,GETDATE())/365.242199)
                      Heh that's awesome

                      I remember doing this years ago in Access and figured that 365.25 was the right number based on leap year being every 4th year

                      If scientifically speaking, we have 365.242199 days a year, then I guess at some distant future point in time we will have a leap year that doesn't leap. (skip the leap day)

                      Comment

                      Working...
                      X