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

High to low sort on calculated field on report

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

    High to low sort on calculated field on report

    I have a report that has a break on equipment as well as a list of work orders for each equipment which shows labour costs. I have a calculated field that shows the total labour cost of all work orders for each equipment but would like to sort the report to show, the equipment with the maximum work order labour cost first, then the next equipment down to the lowest.

    Any easy way to do this? It's beyond my talents. Thanks.

    #2
    Re: High to low sort on calculated field on report

    Only if you can populate a table field with the value on which to sort (likely tablesum() or dbsum()). The Alpha report engine doesn't precalculate values like that. It selects the records according to your filter and groups them and starts printing. The report is done by the time it has reached all the records necessary for computing your max cost.
    There can be only one.

    Comment


      #3
      Re: High to low sort on calculated field on report

      D,

      The field Stan mentions could be put in the parent table of your set, and then populated with a saved update operation. The update operation would be based on the parent table of your set and would use an expression that summed the labor costs from your child table. As Stan mentions, tablesum() is a likely candidate for that expression.

      Comment


        #4
        Re: High to low sort on calculated field on report

        Possibly it could also be done with a posting field rule?
        There can be only one.

        Comment


          #5
          Re: High to low sort on calculated field on report

          Originally posted by Stan Mathews View Post
          Possibly it could also be done with a posting field rule?
          potentially yes. Practically No. Too unreliable.
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment


            #6
            Re: High to low sort on calculated field on report

            If it's a bug they should fix it.
            There can be only one.

            Comment


              #7
              Re: High to low sort on calculated field on report

              Originally posted by dchiass View Post
              I have a report that has a break on equipment as well as a list of work orders for each equipment which shows labour costs. I have a calculated field that shows the total labour cost of all work orders for each equipment but would like to sort the report to show, the equipment with the maximum work order labour cost first, then the next equipment down to the lowest.

              Any easy way to do this? It's beyond my talents. Thanks.
              Are you saying you have two grouping in the report,the outer one is for Equipment and the inner one for Work Order?
              Assuming so, you could sort the group on whichever order you wish.

              Comment


                #8
                Re: High to low sort on calculated field on report

                Originally posted by G Gabriel View Post
                Are you saying you have two grouping in the report,the outer one is for Equipment and the inner one for Work Order?
                Assuming so, you could sort the group on whichever order you wish.
                As you see in report attached, there are 2 sections. The report length could be 100 pages & it would be too time consuming to go thru that many pages to determine which are the assets with largest labour costs hence the need for a SORT.

                I would like this report to sort by equipment with the HIGHEST Total Equipment Labour cost first, then next lower labour cost etc. The Tot_Equip field is a calculated value, its basically the total of all the labour charges for all the work order done on that asset.

                The attached report should have equipment #140 first with total labour value of $4,000, then asset # 300 with a labour cost of $1,400 & lastly asset # 191 with labour cost of $1,100
                Attached Files

                Comment


                  #9
                  Re: High to low sort on calculated field on report

                  Add a group around the equipment group with that calc field, then sort it in a Descending order.
                  Or, instead of getting bugged down with how to sort, really, all you are looking for is 2 numbers, the highest and the lowest.
                  Just add 2 more calc fields to show these two numbers and you do not have to look through the entire report.
                  Use something like dbmax() and dbmin().

                  Comment


                    #10
                    Re: High to low sort on calculated field on report

                    D,

                    You've done a good job at hiding the structure of the set supporting your report.

                    If you're working with a two table set, using one-to-many link, I think the ideas in posts 2 & 3 will help. If you're working with a single table then G's idea in post #9 looks more promising.

                    Comment


                      #11
                      Re: High to low sort on calculated field on report

                      Originally posted by Tom Cone Jr View Post
                      D,

                      You've done a good job at hiding the structure of the set supporting your report.

                      If you're working with a two table set, using one-to-many link, I think the ideas in posts 2 & 3 will help. If you're working with a single table then G's idea in post #9 looks more promising.
                      No I am not hiding anything, I was not aware it was needed. If you need some more details, please ask & I will do my best to answer as I really appreciate all comments & your time to HELP. See attachment.
                      Attached Files

                      Comment


                        #12
                        Re: High to low sort on calculated field on report

                        D,

                        Wow. A one-to-one set. I did NOT see that coming.

                        I see two solutions:

                        a) add a field to your parent table to hold the labor total; then populate it using a saved update operation that sums labor for each piece of equipment. Two step solution: Run the update operation, then run the report.

                        or

                        b) store the labor totals in a separate table containing one record for each piece of equipment. Create a set joining the new table to your parent table with another one to one link. Move your report to the new set. Once its setup you use the same two steps: Populate the total for each piece of equipment in the new table using an update operation; then run your report.

                        tom

                        Comment


                          #13
                          Re: High to low sort on calculated field on report

                          Originally posted by Tom Cone Jr View Post
                          D,

                          Wow. A one-to-one set. I did NOT see that coming.

                          I see two solutions:

                          a) add a field to your parent table to hold the labor total; then populate it using a saved update operation that sums labor for each piece of equipment. Two step solution: Run the update operation, then run the report.

                          or

                          b) store the labor totals in a separate table containing one record for each piece of equipment. Create a set joining the new table to your parent table with another one to one link. Move your report to the new set. Once its setup you use the same two steps: Populate the total for each piece of equipment in the new table using an update operation; then run your report.

                          tom
                          Thanks. I will let you know how we make out.

                          Comment

                          Working...
                          X