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

PAGE_TOTAL()

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

    PAGE_TOTAL()

    I needed to make a change in a report the used the page_total() function. Previous to making changes, this function worked "OK".

    I made numerous changes that did nlot seem to affect this function. I then needed to change the calculated at the bottom of the page from page_total(tlleg-"dayto) to page_total(calc-"pfdayto).

    Now the new calculated field returns the value 999999.99. Worse yet, a previously defined calculated field using page_total() now returns 100000.0.

    I've searched the message board and found that this has been a problem in the past, but no real cause was ever determined.

    To repeat, this report worked "OK" until I changed an allready defined calculated field from page_total(tlleg-"dayto) to page_total(calc-"pfdayto). Now all the page_total() calculations are trashed returning 999999.99.

    Any ideas??

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    #2
    RE: PAGE_TOTAL()

    Wonder if you'd get past the error if you did not nest calc fields inside each other? -- tom

    Comment


      #3
      RE: PAGE_TOTAL()

      Ron,

      Thats what you get for hitting me ..lol

      I am not sure if it is a typo on your end or what, but your syntax looks wrong.

      Try: page_total("calc-"pfdayto")

      Also, obviously, make sure that calc-"pfdayto exists on your report.

      Good seeing you again,

      Scott

      Comment


        #4
        RE: PAGE_TOTAL()

        Ron:
        I was able to replicate the same error exactly as you described it.

        I don't believe there is anything wrong on your end and unfortunately I don't think you can fix this problem either (this is highly speculative on my part).

        I beleive alpha might have to re-work this function.

        Page total is a nice function, but when it gets mixed up with other calculations, it seems to loose it's "sense of direction". Again I am speculating:
        When you use page_tot for a field value, it works fine, it totals the values for that field in this page. On the other hand, when you use it for a calc field, and if that calc field involves values that are drawn from items other than the page, i.e. calc field based on a group that spans across more than one page or spans across the entire report or broken up by some filter or criteria, alpha cannot break those calc values for each page, or perhaps, alpha does not run enough passes to break it up that way. I don't know, I emphasis: I am only guessing.

        Unless somebody has a better explanation or solution, my suggestion is to resort to something other than page_tot(). I would suggest run_total() although it's a RAM hog.
        Gabe

        Comment


          #5
          RE: PAGE_TOTAL()

          Gabe,

          Do you get the same results if you define the expression in terms that do not rely upon other calc fields? i.e. by embedding the actual calculations into the expression instead of asking Alpha to pull the value from a calc field?

          -- tom

          Comment


            #6
            RE: PAGE_TOTAL()

            Yes.
            Gabe

            Comment


              #7
              RE: PAGE_TOTAL()

              Sorry Scott, but it seemed appropriate at the time.

              It doesn't matter if I use the quotes or not.

              Does anyone have any good ideas on how to get totals for the page. In the page footer I have page totals and then running totals. The running totals work just fine.

              Ron
              Alpha 5 Version 11
              AA Build 2999, Build 4269, Current Build
              DBF's and MySql
              Desktop, Web on the Desktop and WEB

              Ron Anusiewicz

              Comment


                #8
                RE: PAGE_TOTAL()

                Ron,

                Not knowing exactly how your report works I can only point you in a direction.

                Try using either TOTAL() or TABLESUM()

                Scott

                Comment

                Working...
                X