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

Count business days

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

    Count business days

    I have a report with the following fields

    "Order_Date"
    "Service_Date"
    "response_time" (a calculate field that is equal to "Service_Date-Order_Date").

    The response_time field should only count business days, not weekends. Does anyone know how to do this?

    Thanks

    Rick

    #2
    RE: Count business days

    Rick-

    I suggest you make a user-defined function

    function BusinessDays as N(FromDate as D, ToDate as D)
    ' you are going to have to figure a short script to do the math
    ' I mean, what IS a business day? Mon - Fri? July 4th? Xmas? Hannukah?
    BusinessDays = result
    end function

    Then where you need it, you simply put
    response_time = BusinessDays(Order_Date,Service_Date)

    Comment


      #3
      RE: Count business days

      Stephen, I think it's apt to be a lengthy script. You'll need something like this:


      pseudo code

      'count days from start to finish, skipping weekends and holidays
      currentdate = begindate
      while currentdate

      Comment


        #4
        RE: Count business days

        Do you want to exclude just weekends or weekends and holidays? The latter is a bit more complicated as it requires a table for holidays that the function has to access. Peter Wayne's Xbasic for Everyone has a section on this topic. You could get a function from there, or if you let me know which you want I can give you a variant of what Peter did in his book.

        Raymond Lyons

        Comment


          #5
          RE: Count business days

          Actually I already provided the functions on this board in Msg ID 34265. Search for that.

          Raymond Lyons

          Comment


            #6
            RE: Count business days

            Rick:
            Here is a sample script that I use to count weekdays between 2 dates.
            It will give you the type of code and syntax to use.
            You may be able to modify the fields to use with your data.
            -------------------------------------------
            'Here is a sample script that you can alter or build on to count the weekdays
            'between 2 dates..

            trace.clear()
            dim global count as n
            dim global count1 as n
            dim global start as d
            dim global end as d
            dim global start_date as d
            dim global j_start as n
            dim global j_end as n
            count=0
            count1=0
            var->start=ctod("01/01/2001")
            trace.writeln ("start -"+dtoc(var->start))
            var->start_date=start
            trace.writeln ("start_date -"+dtoc(var->start_date))
            var->j_start=jdate(start)
            trace.writeln ("j_start -"+str(var->j_start))
            var->end=ctod("02/10/2001")
            trace.writeln ("end -"+dtoc(var->end))
            var->j_end=jdate(end)
            trace.writeln ("j_end -"+str(var->j_end))
            num=j_end-j_start
            for i=1 to num
            start=start+1
            'trace.writeln(str(dow(start)))
            if dow(start)=1 .or.dow(start)=7
            count=count+1
            end if
            if dow(var->start) 1 .and. dow(var->start) 7
            trace.writeln("date is -"+dtoc(start))
            end if
            next i
            count=num-count
            trace.writeln ("Weekdays between "+dtoc(start_date)+" & "+dtoc(end)+" are "+ltrim(str(count)))

            Comment


              #7
              RE: Count business days

              Thanks for everyone's input, I found some information in the "Xbasic for Everyone" book and I must admit, now I'm really confused. Where does this script go? Do I include in the field rules, the report, etc? I've gone through the book several times, and honestly, can not find out how to use a script to update a field. Any I looking to hard for the answer?

              Thanks all,

              Rick

              Comment


                #8
                RE: Count business days

                Rick,

                I guess you need to bone up on user defined functions in the manuals. Peter's script (and my variants of it below) are functions. You create functions in the Control Panel, Code, Functions. For my weekdays functions below you would create a weekdays function as a numerical function with two date parameters (Start_Date and End_Date). Then you could just paste in my code below or type in Peter's code or whatever code you chose to use. From that point on you could use it just like Alpha's built-in functions. It would even show up as an available function in the Expression Builder. That means it could be used in calculated field on a report or even as a calculated field in a field rule. But before you do one of these functions you might want to create the simple one that appears earlier in Peter's book, just to get used creating and using these functions.

                Below is from my earlier post in Msg ID ??(whatever I said it was above).
                Raymond Lyons

                *******************
                The following Weekdays and Workdays functions are based on similar functions in Peter Wayne's Xbasic for Everyone book. The Weekdays function has not been changed much, but the comments are mine, and they may or may not accurately reflect what Peter is doing in his code. For holidays, my app had to deal with long school holiday periods, so instead of requiring that every single day off work ("holiday") date be in a table called Holidays, I changed the table and the function to allow for holiday periods (date ranges) and used my separate Workdays function in a calculated table field "Days" to determine the number of "holidays" (days off work) in the period.

                Raymond Lyons

                function Weekdays as N(Start_Date as D,End_Date as D)
                dim dow1 as n
                dim dow2 as n
                dim weekends as n
                dim offset as n
                If End_Date={}
                End_Date={01/01/0001}
                End If
                If Start_Date={}
                Start_Date={01/01/0001}
                End If

                '**Going to divide by 7 to get weekends, so have to get full weekends in the range
                '** Use offsets to do this.
                '**Each offset below either adds or subtracts weekend days to the date
                '**in the date field. Then just /7 to get the # of weekends in the offset range

                dow1=dow(Start_Date) 'Day of week for the beginning of the date range
                offset=case(dow1=7,2,dow1=1,1,.t.,0) '**7=sat, 1=sun
                Start_Date=Start_Date+offset
                dow2=dow(End_Date) '**Day of week for the last day of the date range
                offset=case(dow2=7,-1,dow2=1,-2,.t.,0) '**7=sat, 1=sun
                End_Date=End_Date+offset

                '**Now just calculate # of weekends and add a fudge factor in the event,
                '**that first - last goes, say, from a Thurs to a Monday

                weekends=int((End_Date-Start_Date)/7)+iif(dow(Start_Date)>dow(End_Date),1,0)
                weekdays=End_Date-Start_Date+1-2*weekends
                end function

                �********************
                The function below uses a 4 field holidays table:
                Hol_Start Date 8 0
                Back_On Date 8 0
                Name_Of_Holiday Char 25 0
                Days Numeric 3 0
                The Days field above is a calculated field:
                WEEKDAYS(HOL_START,IF(BACK_ON={},HOL_START,BACK_ON))
                Also note that I use Back_On to mean the date one comes back to work, not the last day off work in the period. With adjustments you could do it the other way.

                function Workdays as N(First as D,Last as D,Name_of_Hol_Tbl as C)
                dim dow1 as n
                dim dow2 as n
                dim weekends as n
                dim nholidays as n
                dim offset as n
                dim hol as p 'pointer to the holidays table
                dim ip as p
                dim query.description as c
                dim query.filter as c
                dim query.options as c
                dim query.order as c
                dim fld as p 'pointer to the field in holidays
                dim field_name as c
                dim indx as p
                If Last={}
                Last={01/01/0001}
                End If
                If First={}
                First={01/01/0001}
                End If
                on error goto no_holiday_table
                hol=table.open(Name_of_Hol_tbl)
                on error goto 0

                fld=hol.field_get(1) '**Pointer to 1st field in the file
                if fld.type_get()"D" then '**Make sure the 1st field is a date
                workdays=-1
                exit function
                end if
                '**above was just to be safe
                field_name=fld.name_get() '**name of the 1st field-will be used below

                '**1st, divide by 7 to get weekends, so have to get full weekends in the range
                '** Use offsets to do this. (NOTHING HERE TO DO WITH HOLIDAYS TABLE)
                '**Each offset below either adds or subtracts weekend days to the date
                '**in the date field. Then just /7 to get the # of weekends in the offset range

                dow1=dow(first) '**Day of week for the beginning of the date range
                offset=case(dow1=7,2,dow1=1,1,.t.,0) '7=sat, 1=sun
                first=first+offset
                dow2=dow(last) '**Day of week for the last day of the date range
                offset=case(dow2=7,-1,dow2=1,-2,.t.,0) '7=sat, 1=sun
                last=last+offset
                '**Now just calculate # of weekends and add a fudge factor in the event,
                '**that first - last goes, say, from a Thurs to a Monday

                weekends=int((last-first)/7)+iif(dow(first)>dow(last),1,0)

                '**NOW DO TO HOLIDAYS***

                dim Holidays_count as n
                Holidays_count=0
                hol.index_primary_put("Hol_Start")
                hol.fetch_first()
                WHILE .not. hol.fetch_eof()
                IF BETWEEN(hol.Hol_Start,first,last)
                Holidays_count=Holidays_count+hol.days
                END IF
                hol.fetch_next()
                END WHILE

                '**Finally, just calculate the workdays

                workdays=last-first+1-Holidays_count-2*weekends
                hol.close()
                exit function

                no_holiday_table:
                on error goto 0
                workdays=-1
                exit function
                end function

                Comment


                  #9
                  RE: Count business days

                  Thanks for all your help Raymond and all. I finally got this figured out this morning, could not have done it with all of your help!

                  Thanks again,

                  Rick

                  Comment

                  Working...
                  X