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

External & Calculated Field Complications (Reports)

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

    External & Calculated Field Complications (Reports)

    Hello,


    I have a question about the use of external & calculated fields in my reports.
    I basically have a report which has a linked report in it. Let's name the parent report 'Report A' and the child report 'Report B'. A is of free-form type. B is a layout-table.

    Report A

    Contains a Group Header, a Detail section (which contains Report B), a Report Footer and a Page Footer for Report section. The Group part surrounds only the detail section, but I don't need a Group Footer part.

    Report B

    I have a Detail section, surrounded by a Group Header and Group Footer section, nothing else. I also have a ton of calculated fields defined. The Header section merely has a title field, the title being extracted from the data base. The Detail section contains, well, the detailed records I need. And finally, the Footer section, prints some totals. For example, let's say 3 totals. 'Total 1' equals the sum of a field ('Price', for example) in the detail section. 'Total 2' equals 'Total 1' plus 10% of 'Total 1'. And last, but not least, 'Total 3' equals 'Total 2' plus 20% of 'Total 2'. Yes, it's a little bit overwhelming, but the important thing is that 'Total 3' is calculated successively and is the final value we're actually interested in. Now, this report prints me 2 separate groups, breaking on a certain ID. First group (Group 1) has a Title ('Title X', for example), certain records in Detail and a final 'Total 3' printed. Second group (Group 2) has a different title ('Title Y'), different records in Detail and an other final 'Total 3' printed, different from the one in Group 1.

    Hope this is a good description - my reports are pretty complicated to describe them fully, so I largely summarized the structure of them.

    What I need to is to do some calculations and send it via a new field to Report A.
    Let's say Total3 for Group 1 equals 1200 and for Group 2 equals 280. We also have two percentages, N = 20% and M = 50%.
    Here are the equations I need to do:


    Value1 = if(Title = "Title X", (Total3 * N)/100, 0)
    Value2 = if(Title = "Title Y", (Total3 * M)/100, 0)
    Sum = Value1 + Value2


    So if we do the math with the above presented data, for Title X, Value1 equals 240 and for Title Y, Value2 equals 140. Sum equals 380.
    I need to send the field 'Sum' to Report A as an External Field and print 380. I print it in the detail section of Report A.
    The problem is that it will only send 140. My guess is because these calculated fields reset at the end of each group. So yes, Report B does print the two values separately, but I can't seem to find a way in printing the Sum as 380 with the above mentioned structure, in neither of the Reports.

    Do you have any idea how could I solve this problem?

    Thanks in advance!

    David
    Tags: None
    #2
    Re: External & Calculated Field Complications (Reports)

    A sample database would go a long way towards a quick solution.

    Likely you will have to use tablesum() expressions to derive the totals you want.
    There can be only one.

    Comment

      #3
      Re: External & Calculated Field Complications (Reports)

      Ah, it will take a little bit of time. I'll return here with a sample database then as soon as possible.

      Thanks!

      Comment

        #4
        Re: External & Calculated Field Complications (Reports)

        Here's the sample database as promised ("test_case.rar"). I've created the db using Navicat. Sorry for taking so long.
        There's basically a parent table (Report A uses the parent table), a child table (Report B uses it) and a percentages table (both reports use it).

        However, I don't really understand why do you need the sample database. If you want to create the solution in the SQL query, I already have thought of that, and because of the current complexity in my code and because of the fact that I would need to add the same amount of code, I would rather avoid doing so. As I said, I merely summarized the description, but for example, in order to get to 'Total 3', I'm doing much more calculations using a lot of different fields. So, in order to avoid this and to have efficiency where possible, I need to find a way to do it, directly in the report editor.
        Attached Files

        Comment

          #5
          Re: External & Calculated Field Complications (Reports)

          This is the first you mentioned sql. I was thinking of a solution in a dbf situation.
          There can be only one.

          Comment

            #6
            Re: External & Calculated Field Complications (Reports)

            Sorry, I forgot to mention it. Yes, I'm using SQL with my reports.

            Comment

              #7
              Re: External & Calculated Field Complications (Reports)

              I don't have much experience with sql reports. Perhaps you can retrieve the necessary values with an sql_lookup() function?
              There can be only one.

              Comment

                #8
                Re: External & Calculated Field Complications (Reports)

                I don't think so because that one works directly with the database. I need to retrieve the values after they have been calculated in the report editor, through calculated fields, using the Xbasic language. So, I guess I need an Xbasic function that could do this.

                Comment

                Previous template Next
                Working...
                X