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
Devcon 2020 Goes Virtual! LEARN MORE >

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

using previous function in a report calc field

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    using previous function in a report calc field

    In Alpha 5 V8 (Build 1965, System addins, Build 3156)I am using the previous() function in a report, based on a primary index in a calc field. Here is what I have in my report for this function:

    unit1use = unit1-previous("unit1")

    I have also used

    unit1use = unit1-(previous("unit1"))

    just in case there is an ordering (parsing) issue in the function.

    where unit1use is a calculated field in the report, unit1 is the current value, and I need the difference between the two (current value is guaranteed to be larger than the previous record value for unit1).

    The primary key is numeric (integer) and is used as the primary index.

    When I allow the report to use/select all records, the previous () function works correctly (i.e., first to last record), all calc unit1use values in the report are correct. However, if I select (based on a key/primary index), say two records that are in sequence (primary key values selected are 244, 245, and in logical sequence), the values are incorrect. The calc actually produces the value of the field in previous record, not the difference between the field in the two records.

    This function worked as expected in Alpha 5 V1, but doesn't appear to work as expected in the above scenario.

    I intend to try this also in Alpha 5 V9, but need it to work in V8 (or find out if I am not using the function correctly, or not setting some conditions required.

    Any suggestions or similar experiences would be appreciated.

    Thanks,

    Richard

    Additional Info: I should have mentioned that I'm using this within a Set, and that the index (according to the documentation) should be using the primary index by default.
    Last edited by Richard Kosick; 04-13-2009, 12:21 AM. Reason: additional info
    Tags: None
    #2
    Re: using previous function in a report calc field

    Hi Richard,

    Have you tried to use a named Index instead of the default?
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment

      #3
      Re: using previous function in a report calc field

      I don't know if it would make any difference but the latest update to V8 is Build 1980, sytem add-ins build 1363.

      I'm also curious why you don't have a single field in the table with the calculated value instead of doing the calculation in the report?

      Comment

        #4
        Re: using previous function in a report calc field

        Having the latest build could make a difference but do not remember an issue with the previous() function....build 1980, build 3163 is actually the last build available.

        Robert,
        a single field in the table with the calculated value instead of doing the calculation in the report?
        Actually the way Richard is doing it is the most acceptable method as most deem it totally unnecessary to have a field for what a calculated field can do. IOW, If a value is not needed to be stored or if it is going to be in a constant state of change, then a calculated field is the way to go (although recently I did find a specific reason beyond this situation in which it made sense to store such a value--no need to confuse the issue here though).

        Not having used the previous() function recently (ever?), I would have to experiment a bit with it to even guess at the problem...especially seeing as how it seems Richard has a very specific scenario going on (sample maybe ?).
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment

          #5
          Re: using previous function in a report calc field

          Just got back on the forum tonight. Thanks all for your input. After my post, I did go back and specify the desired (primary) index, and that seemed to cure the symptoms. And since I am using a set, only the parent table will be referenced (according to the documentation). Actually, I'm just now redoing a small app that I've run on Alpha 5 V1 for several years (prior to that on Alpha 4). The app always worked on A5V1. But forcing the index works, so no need to question that.

          The DB record count is fairly small (< 1000 records), and I use the app for a monthly billing scenario and analytical reports over longer periods (quarterly, monthly).

          I'll revisit the Alpha 5 V8 update pages, but thought I had downloaded the latest. But, per the much appreciated input, I must not have.

          I will eventually port the Alpha 5 V8 version to A5V9, and install as a runtime app.

          Comment

          Previous template Next
          Working...
          X