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

Trailing Twelve Months Calculation

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

  • Trailing Twelve Months Calculation

    All --

    I have a table of monthly account balances for the past four years. I would like to create a table of trailing twelve months balances from this table. In other words, each value in the new table contains the average of the last twelve values in the initial table. It would have only 36 values instead of the 48 in the original table.

    How can I do this?

    -- Dick James

  • #2
    Re: Trailing Twelve Months Calculation

    I suggest you get pencil and paper and write down the steps you'd have to take in order to do this, assuming you had to do this by hand. Begin with a single account, in the most recent month. Then think about how to convert your sequence into code.

    Comment


    • #3
      Re: Trailing Twelve Months Calculation

      OK. The table name is tblMonthlyBalances, and it contains one record for each month. In that record there are several fields, but the two I propose to use are the JulianDateofBalance field and the MonthlyBalance field. I propose to put the calculated trailing twelve months balance in a third field. So the table layout is:

      JulianDateofBalance (N)
      MonthlyBalance (N)
      TTMBalance (N)

      The steps would be these:

      1. Order the table on JulianDateofBalance with newest first. (I know how to do this.)

      2. Starting with the first value, if there are fewer than 11 prior values, then stop. (Don't know how to do this.)

      3. Add the 11 prior values to the current value to give a total. (Don't know how to do this.)

      4. Divide the total by 12 and store it in the TTMBalance field. (I can do this if I can figure out how to do steps 2. & 3. above.)

      Any suggestions?

      -- Dick James

      Comment


      • #4
        Re: Trailing Twelve Months Calculation

        Originally posted by DickJames View Post
        Any suggestions?
        Here is how I would do it:
        Code:
        ''========================LOOP  & FETCH
        tbl = table.open("tblMonthlyBalances")
        idx = tbl.index_primary_put("JulianDateIndexName") 
        nrecs = idx.records_get()
        Dim vBalArray[nrecs] as n
        
        i = 1
        vRunTotal = 0
        
        tbl.fetch_first()
        while .not. tbl.fetch_eof()
            vBalArray[i] = tbl.MonthlyBalance 
            vRunTotal = vRunTotal + tbl.MonthlyBalance 
            
            IF i >= 12
                vRunAverage = vRunTotal/12
                tbl.Change_Begin()
                    tbl.TTMBalance = vRunAverage
                tbl.Change_end(.t.)
                
                vRunTotal = vRunTotal - vBalArray[i-11]        
            END IF
        
            statusbar.percent(i,nrecs)
            i = i + 1
        tbl.fetch_next()
        end while
        
        tbl.close()
        vTitle1 = "FINI" 
        vMsg1 =  "Balances Updated!"
        ui_msg_box(vTitle1, vMsg1,UI_INFORMATION_SYMBOL)
        END
        I don't know if there is another way (there always is). You need to make sure you have an index for the date field. I just called it "JulianDateIndexName". You could attach this script to a button on your form. I haven't tested the script so I might have made a mistake in logic?

        Good luck!


        P.S. If you don't know xbasic, this is the place to start. Even if you don't, xbasic is almost readable as is - esp. for a smart guy like you.;)
        Last edited by Peter.Greulich; 02-21-2010, 01:46 PM.
        Peter
        AlphaBase Solutions, LLC

        [email protected]
        https://www.alphabasesolutions.com


        Comment


        • #5
          Re: Trailing Twelve Months Calculation

          Peter --

          I'm not sure I'm all that smart, but I was able to make your code work for me. I changed your statement:

          tbl.index_primary_put("JulianDateIndexName") to tbl.index_primary_put() because record number order is also juliandate order in this table, and the statement was causing an error.

          It seems to work great! I'm surprised A5 doesn't have some built-in function to do this because it is a very common way to look at financial trends.

          Thanks very much for your help.

          -- Dick James

          Comment


          • #6
            Re: Trailing Twelve Months Calculation

            Originally posted by DickJames View Post
            ... I changed your statement:

            tbl.index_primary_put("JulianDateIndexName") to tbl.index_primary_put() because record number order is also juliandate order in this table, and the statement was causing an error.
            From the controlpanel, click on your table and select design/indexes and create an index for the date field. Plug whatever name you give the index into the script. It's not a good idea to rely on record order. Someday that might bite you.
            Peter
            AlphaBase Solutions, LLC

            [email protected]
            https://www.alphabasesolutions.com


            Comment

            Working...
            X