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

Lookup Predefined Date Range

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

    Lookup Predefined Date Range

    I noticed on the Web side there is a tool for doing this already: Whereby the user selects 'This Month' from a list and a date range is returned for startdate and enddate args that can then be used in a query. I would like to replicate this feature in a lookup on the desktop.

    Here is my lookup list with the return values (vRng) - another lookup list selects the year (vYear):
    <Show All>|0
    Today|T
    This Week|W
    Last Week|L
    January|1
    February|2
    March|3
    April|4
    May|5
    June|6
    July|7
    August|8
    September|9
    October|10
    November|11
    December|12
    1st Quarter|Q1
    2nd Quarter|Q2
    3rd Quarter|Q3
    4th Quarter|Q4

    My Select Case statement should be able to test vRng and get the start & end dates for vYear. So far I have the Quarters only:

    Code:
        case vRng = "Q1"
            q = date_quarterstartend(val(vYear),1)        
        case vRng = "Q2"
            q = date_quarterstartend(val(vYear),2)
        case vRng = "Q3"
            q = date_quarterstartend(val(vYear),3)
        case vRng = "Q4"
            q = date_quarterstartend(val(vYear),4)
    If vRng is Q4 and vYear is 2017 then I can get this to set my range:
    ?q.startdate
    ={10/01/2017}
    ?q.enddate
    ={12/31/2017}
    vBegDate = q.startdate
    vEndDate = q.enddate

    Any ideas on how to get the others - like for the weeks and months?

    Edit: found this for the months
    Code:
    case vRng = between(vRng,"1","12")
    	vBegdate = date_value(val(vYear),val(vRng),1)
    	vEnddate = month_end(vBegdate)
    Now for the weeks...
    Last edited by MoGrace; 12-17-2017, 02:20 PM.
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    #2
    Re: Lookup Predefined Date Range

    What is a "week"? Sunday through Saturday?

    ? date()-dow(date())+1
    = {12/17/2017}
    ? date()-dow(date())+7
    = {12/23/2017}
    There can be only one.

    Comment


      #3
      Re: Lookup Predefined Date Range

      Well there goes 4 hours I could have spent better - thanks Stan! You always make it look simpler than it does to me...

      Then to get the previous week:

      ? (date()-dow(date())+1)-7
      = {12/10/2017}
      ? (date()-dow(date())+7)-7
      = {12/16/2017}

      Perfect!
      Last edited by MoGrace; 12-17-2017, 07:01 PM.
      Robin

      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

      Comment


        #4
        Re: Lookup Predefined Date Range

        Syntax error in this code for the month - note that Between() is either T or F ...:
        Code:
        case vRng = between([COLOR="#FF0000"]vRng,"1","12"[/COLOR])
        vBegdate = date_value(val(vYear),val(vRng),1)
        vEnddate = month_end(vBegdate)
        But Between() will not find numbers entered as characters (returns .F.) - but this works:

        Code:
        case between([COLOR="#0000CD"]val(vRng),1,12[/COLOR])
        vBegdate = date_value(val(vYear),val(vRng),1)
        vEnddate = month_end(vBegdate)
        And I needed to move the case statement to be before the others.
        Last edited by MoGrace; 12-17-2017, 08:09 PM. Reason: still wrong...
        Robin

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

        Comment


          #5
          Re: Lookup Predefined Date Range

          case vRng = between(vRng,"1","12")
          Shouldn't that be

          case between(vRng,"1","12")

          Code:
          But Between() will not find numbers entered as characters (returns .F.)
          It will but the usual left to right character comparison affects the outcome

          vrng = "06"
          ? between(vrng,"01","12")
          = .T.
          There can be only one.

          Comment


            #6
            Re: Lookup Predefined Date Range

            normally when I use numbers as characters I do use padL(), but in this case val(vRng) works just fine.
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment

            Working...
            X