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

Problems with page_total

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

    Problems with page_total

    Some years ago, there were several threads regarding issues with the page_total function on reports. I am still having problems with it. Does anyone know if it was ever fixed, or at least any reasonable workarounds?

    Here is what I experience (same as I reported years ago):

    Every now and then, and with no discernible pattern, I get 9999999.99 as the page_total result.

    Another strange thing is that even when it gets close to the real result, it can be thrown off by making the detail section a little larger or a little smaller. For example, If I want just 6 records on a page, I can play with the size of the detail section and get say one more or one less record on the page. But the result MAY show a total that seems to include the next record on the next page. That is, the page will show say six records, but the result will compute based on those 6 records plus the first record that will show on the next page. If I make the detail section just a bit smaller, I can play with it to get still just the 6 records I want, and the total will correctly reflect just those 6 records. This is strange stuff. Does anyone understand what is going on here?

    This is all on the localhost. Then when I publish to my remote server, the page_total does not display a number at all. It just displays the name of the calculated field, in my case, pagefee. So instead of a number, the filed just displays the word "pagefee".

    Any ideas?

    Gary
    Gary S. Traub, Ph.D.


    #2
    Re: Problems with page_total

    Alpha displays the name of a calculated field when it cannot resolve the intended value/computation.

    Unfamiliar with the term "localhost". Is this an Application Server question in the desktop area?
    There can be only one.

    Comment


      #3
      Re: Problems with page_total

      localhost is when you use your own computer as the host to your webpages, Are you referring to a web application?
      If so, this is not the right section of the message board, but regardless, page total from what I remember is not really reliable. I haven't used it since way back when.
      I can't swear to it, but I am sure you can design your own calc value to subtitute for page_total.

      Comment


        #4
        Re: Problems with page_total

        Thanks Stan and Gabe,

        Yes, local host refers to the web side, but page_total refers to the desktop side, so I posted it to both forums.

        Page_total not working is a big problem for me. I gather that I am in the minority regarding the need for a page total.

        So far, I have come up with a way around that involves calculating the page total and writing it to an additional field within the table, and then using that value in place of the page_total function. It works, but because of the pre-processing required, slows down the report process. With just a few records, not that noticeable, but with even just hundreds, it can take an additional 10 to 20 seconds, and if it were say a thousand or more records, it would be very slow. For now, I'll use this approach, until I or anyone else comes up with something better.

        Any other suggestions would certainly be welcomed though ...

        Gary
        Gary S. Traub, Ph.D.

        Comment


          #5
          Re: Problems with page_total

          Would run_total() work for you?

          Comment


            #6
            Re: Problems with page_total

            What other work-around depends on how you determine the number of records in a page. This is going to be hard to play with without a real life example, hopefully one that is not too involved.

            Comment


              #7
              Re: Problems with page_total

              I tried run_total before, and it doesn't work for my needs. An account might be split over several pages, with a maximum of 6 line items on a page. Some will have less, but never more than 6. I need a page total at the bottom of EVERY page.

              Thanks anyway!

              Gary
              Gary S. Traub, Ph.D.

              Comment

              Working...
              X