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

Adding a week number to an existing table

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

  • Adding a week number to an existing table

    I have been asked to add a week number on to an invoice table, these will run from the 1st August each year e.g.
    Week No From To
    1 01-Aug 07-Aug
    2 08-Aug 14-Aug
    3 15-Aug 21-Aug
    This is so a report can be produced to show the number of people booking with us each week.

    So far I have created a new table consisting of two fields, week number and date (365 records with week numbers 1

  • #2
    Re: Adding a week number to an existing table

    Originally posted by Judith View Post
    I have been asked to add a week number on to an invoice table, these will run from the 1st August each year e.g.
    Week No From To
    1 01-Aug 07-Aug
    2 08-Aug 14-Aug
    3 15-Aug 21-Aug
    This is so a report can be produced to show the number of people booking with us each week.

    So far I have created a new table consisting of two fields, week number and date (365 records with week numbers 1
    Did your message get truncated?
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


    • #3
      Re: Adding a week number to an existing table

      Judith,

      I believe you are going to have to construct a table of week numbers and corresponding actual start and end dates for some number of years into the future. If you rely solely on the start

      01-Aug
      08-Aug
      15-Aug
      etc

      your resulting retrieval of the week number for 03-04-someyear will be week 30 for non leap years but 31 for leap years.
      There can be only one.

      Comment


      • #4
        Re: Adding a week number to an existing table

        If you have 365 entries for a year with 366 entries for a leap year, you can make a set or mapped table to do what you want.

        Link by the date in the invoice table to your week table to get the week number.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment


        • #5
          Re: Adding a week number to an existing table

          Week numbers are actually a specific legal entity.
          You might want to rethink the logic.
          See our Hybrid Option here;
          https://hybridapps.example-software.com/


          In fairness to alcohol, I have done some stupid things when I was sober too!

          Comment


          • #6
            Re: Adding a week number to an existing table

            Why not just calculate the week number? You'd probably need to store the starting date in a variable, or set it before calculating the week number

            int((*days_between(date(),{1/8/17}))/7)+1

            seems to do the trick.

            Comment


            • #7
              Re: Adding a week number to an existing table

              *days_between() is a function introduced in AA/V12 and not available in V11.
              There can be only one.

              Comment


              • #8
                Re: Adding a week number to an existing table

                Borrowing Jon's thought, someone see if this works or rather if it breaks down somewhere.

                Code:
                dt = {01/01/2018}
                ? int(if(dt< ctod("08/01/"+cyear(dt)),dt-ctod("08/01/"+cyear(addyears(dt,-1))),dt-ctod("08/01/"+cyear(dt)))/7)+1
                = 22
                dt = {07/30/2018}
                ? int(if(dt< ctod("08/01/"+cyear(dt)),dt-ctod("08/01/"+cyear(addyears(dt,-1))),dt-ctod("08/01/"+cyear(dt)))/7)+1
                = 52
                dt = {07/31/2018}
                ? int(if(dt< ctod("08/01/"+cyear(dt)),dt-ctod("08/01/"+cyear(addyears(dt,-1))),dt-ctod("08/01/"+cyear(dt)))/7)+1
                = 53
                
                dt = {08/01/2018}
                ? int(if(dt< ctod("08/01/"+cyear(dt)),dt-ctod("08/01/"+cyear(addyears(dt,-1))),dt-ctod("08/01/"+cyear(dt)))/7)+1
                = 1
                If anyone wants to do a visual check.

                Code:
                dt = {08/01/2017}
                for qx = 1 to 2000
                wn = int(if(dt< ctod("08/01/"+cyear(dt)),dt-ctod("08/01/"+cyear(addyears(dt,-1))),dt-ctod("08/01/"+cyear(dt)))/7)+1
                save_to_file(padl(alltrim(str(wn)),2,"0")+" _ "+dtoc(dt)+crlf(),"[COLOR="#FF0000"]P:\temp\week nums.txt[/COLOR]",.T.)
                dt = dt + 1
                next
                Last edited by Stan Mathews; 02-28-2018, 11:15 AM.
                There can be only one.

                Comment


                • #9
                  Re: Adding a week number to an existing table

                  OK, how about

                  int((jdate(test)-jdate({1/8/17}))/7)+1

                  where test is the date to check against

                  Comment


                  • #10
                    Re: Adding a week number to an existing table

                    Doesn't that require resetting the base date each year? Not that it is wrong to do it that way.
                    There can be only one.

                    Comment


                    • #11
                      Re: Adding a week number to an existing table

                      Base date would need setting or calculating before/during the week number calculation.

                      Comment


                      • #12
                        Re: Adding a week number to an existing table

                        Code:
                        dim start as d={8/1/17}
                        dim end as d
                        dim wk_No as n
                        
                        end={8/8/17}
                        wk_No=min(int((end-start+7)/7),53)
                        ?wk_No
                        = 2
                        
                        end={8/14/17}
                        wk_No=min(int((end-start+7)/7),53)
                        ?wk_No
                        = 2
                        
                        end={8/15/17}
                        wk_No=min(int((end-start+7)/7),53)
                        ?wk_No
                        = 3
                        
                        end={8/16/17}
                        wk_No=min(int((end-start+7)/7),53)
                        ?wk_No
                        = 3
                        
                        end={7/31/18}
                        wk_No=min(int((end-start+7)/7),53)
                        ?wk_No
                        = 53

                        Comment

                        Working...
                        X