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

Date criteria request

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

    Date criteria request

    I need to create a report with Year to date info, but because of the business, each "week" ends on a Saturday. If any part of the week is in a particular year, all of that week is in that year, so those dates in that week which, in actuality, are in the current year, are to be included in the previous for reporting. Likewise, those dates which in actuality are at the beginning of the following year will need to be included in the current year for reporting purposes.

    If this is not totally confusing, I can probably muck up the situation just a bit more with an example .

    Since January 1, 2000 was a Saturday, the report would not include 1/1/200 in the year to date information, because that is part of last year's report.

    This year's report will include 1/2/2000 through 1/6/2001, since part of the last "week" of the year was in 2000.

    So, how do I write an expression for year to date to include the correct dates? Obviously year(date()) will not work.

    Thanks for the assistance.

    Jay Talbott
    Jay Talbott
    Lexington, KY


    #2
    RE: Date criteria request

    Jay,

    To answer your question, you need to specify what day of the week does start for you. E.g. If Jan 1 is on a sunday is that week included in the previous year? How about Monday?

    If it starts on a Tuesday through Saturday, I'll assume the days through Saturday would be in the previous year. However if Jan 1 is on a Monday, what year do the days through Saturday go? Sunday Jan 1st I'll assume is all in the current year.

    It would look probably something like this;

    StartDay=CTOD("01/01/"+CYEAR(DATE()))+ IF(DOW(CTOD("01/01/"+CYEAR(DATE())))>1,
    8-DOW(CTOD("01/01/"+CYEAR(DATE()))),0)

    Regards,

    Ira J. Perlow
    Computer Systems Design & Associates
    [email protected]
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


      #3
      RE: Date criteria request

      Ira,

      Thanks for your prompt reply.

      To clarify, weeks always run Sunday through Saturday, regardless of what day Jan 1 falls on. The year 2000 started on Saturday, so the first full week which was actually in 2000 started on Jan 2.

      The year 2000 (for their reporting purposes) will run through Jan 6, 2001 since some part of that week started in 2000.

      What I am looking for is a perpetual start date and end date for the reporting year. For 2000, I know that this would be Jan 2, 2000 through Jan 6 2001.

      Thanks again for your help.

      Jay
      Jay Talbott
      Lexington, KY

      Comment


        #4
        RE: Date criteria request

        You can get some strange period ends when using a 4,4,5 balance sheet, or, as in your case, I presume a 52/53 week fiscal year. I suspect that you'll need more than an expression. Perhaps a table of fiscal years with beginning and ending dates to compare against. You might want all "reporting tables" to have a field to lookup and store the fiscal year. You could try using a "LookupC" (closest value) to return the proper fiscal year in the records.

        Comment


          #5
          RE: Date criteria request

          Jay,

          Beginning of year =

          If 1st falls on Saturday, subtract 6
          If 1st falls on Friday, subtract 5
          If 1st falls on Thursday, subtract 4
          If 1st falls on Wednesday, subtract 3
          If 1st falls on tuesday, subtract 2
          If 1st falls on Monday, subtract 1
          If 1st falls on Sunday, Hallelujah!


          End of year =

          If 31st falls on Sunday, add 6
          If 31st falls on Monday, add 5
          If 31st falls on tuesday, add 4
          If 31st falls on Wednesday, add 3
          If 31st falls on Thursday, add 2
          If 31st falls on Friday, add 1
          If 31st falls on Saturday, Hallelujah!


          -- tom

          Comment


            #6
            RE: Date criteria request

            Tom,

            For the beginning of the year, you have to add values, not subtract them. Nevertheless, that is what my equation I published before does. Again it is;

            StartDay=CTOD("01/01/"+CYEAR(DATE()))+
            IF(DOW(CTOD("01/01/"+CYEAR(DATE())))>1,
            8-DOW(CTOD("01/01/"+CYEAR(DATE()))),0)

            An alternative version (one I was too lazy to ascertain initially) is;

            StartDay=CTOD("01/01/"+CYEAR(DATE()))+
            MOD(8-DOW(CTOD("01/01/"+CYEAR(DATE()))),7)

            Obviously an end date would have DATE() substituted with ADDYEARS(DATE(),1) in the above and then subtract 1 as in;

            EndDay=CTOD("01/01/"+CYEAR(ADDYEARS(DATE(),1)))+
            IF(DOW(CTOD("01/01/"+CYEAR(ADDYEARS(DATE(),1))))>1,
            8-DOW(CTOD("01/01/"+CYEAR(ADDYEARS(DATE(),1)))),0)-1

            or alternatively,

            EndDay=CTOD("01/01/"+CYEAR(ADDYEARS(DATE(),1)))+
            MOD(8-DOW(CTOD("01/01/"+CYEAR(ADDYEARS(DATE(),1)))),7)-1

            Regards,

            Ira J. Perlow
            Computer Systems Design & Associates
            [email protected]
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions

            CSDA Code Utility
            CSDA Screen Capture


            Comment

            Working...
            X