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

sub-report limitations?

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

    sub-report limitations?

    Hey out there...this one's really stumping me. I think I may have found a limitation of Alpha V - no, really! Can't really believe it, myself...but I've tried everything. Here goes:

    I have a report designed on a table in which the total and average calculated fields work properly. I have this same table in a set, and have designed a report that contains the exact data in a sub-report, as is in the original stand-alone table report. I have duplicated the exact same calculations, but they don't work in the sub-report.

    Anything I should know about sub-report limitations? That's the only thing I can think of.

    Is there a way to import a report into another report instead of creating a sub-report via a new object?

    Thanks for any insight.
    Wanda
    Tags: None
    #2
    RE: sub-report limitations?

    If you're trying to calculate totals and averages for all records in the linked child table, I'm not sure you can do it in a subreport. As I understand it subreports are primarily intended for records linked to the current parent record, sort of like a group. It's possible to generate totals and averages for the currently linked child records using a subreport (which of course would be a subset of all the records in the child table), but I don't think it can 'look ahead' or 'look behind' to include other records in the child table *not linked* to the current parent record. Having said this, don't accept it as gospel. My experience with subreports is quite limited. On the other hand, if you are trying to total and average just the currently linked child records, I think it can be done, but you'll probably have to redefine the calculated fields.

    Comment

      #3
      RE: sub-report limitations?

      Hi Tom,
      Yes, I am only trying to calculate a total and an average of only the child records in the sub-report that match the parent. The data in the parent is actually reported in a group break in the main report, with no data in the detail section of the main report.

      I can easily get a total and average in the sub report - but I can't get it to count (or total) records in the child that meet a certain criteria - i.e. the end date field being blank, or the LOS field having data greater than .00001.

      BTW - the report prints only records that pertain to one individual at a time - via a variable at print time.

      Thanks,
      Wanda

      Comment

        #4
        RE: sub-report limitations?

        Hi Wanda,

        I have recently created a report with 10 subreports, Mon am, Mon Pm, Tuse am, Tues pm etc.

        Each subreport has it's own subtotal, in my case count bases on a calculated field.
        This is my total count for Frid pm based ont the calc field to check on a condition before the count.

        total(Calc->If_fripm,GRP->detail,GRP->Subreport 10:detail)

        Michael

        Comment

          #5
          RE: sub-report limitations?

          Thanks, I'll work with the idea of "GRP->detail" in my "IF" calculation and see what I get. Will let you know.

          Comment

            #6
            RE: sub-report limitations?

            Michael,

            IT WORKS!!!! I owe you one! The trick to getting calculations to work in sub-reports, I think, now, is to be real specific about the grouping. What finally ended up working was including the :detail at the end of my calculations. Who would-a-thunk?! I've never had to use the :detail before, and didn't even know the little devil existed.

            Thanks so much...
            Wanda

            Comment

              #7
              RE: sub-report limitations?

              I have used lots of reports with subreports and the biggest downside is being able to justify the lengths so that you can have each subreport total in a neat row. I have designed a work around but it is limited. What I do is create a dummy subreport and base this on a selection of records that will always be larger than the data subreports. I then format the dummy with lines and boxes etc and place the data totals in the footer of the dummy subreport.

              Michael

              Comment

                #8
                RE: sub-report limitations?

                Huh?

                Now I'm confused, again...you wrote:
                "...biggest downside is being able to justify the lengths ..."

                Lengths of what? Fields? The report, itself? Justify - as in the typographical term?

                "...create a dummy subreport and base this on a selection of records that will always be larger than the data subreports..."

                Is the data for the dummy subreport in a dummy database? What is always larger...the data, or the size of the subreport?

                "...I then format the dummy with lines and boxes etc and place the data totals in the footer of the dummy subreport..."

                Are the lines and boxes used with the totals in the dummy footer? If it's a dummy, then how can it give you the results you need?

                I would like to understand this, as it seems it could come in handy for me. Maybe you can send me a printscreen via a Word attachment in an email to my email address. I don't know if this Messageboard can handle printscreen.

                Thanks, Michael,
                Wanda






                Maybe you can do a screen print, paste into Word, and send to my private email.

                Comment

                  #9
                  RE: sub-report limitations?

                  If you can imagine three subreports. Sub 1 has 10 records in detai, sub 2 has 20, sub3 has 30. If you format your subreports into boxes with totals in each footer you will end up with an unsightly staggered view.

                  To get each footer of the varying subreport length on one line, create an extra dummy subreport without any detail but filtered on records that will always be longer than the largest subreport. You can then format this dummy with lines or boxes and place your other subreport totals in the footer of the dummy.

                  A bit of fiddling to get it right but a pleasing finished appearance.

                  I have emailed you a sample of mine.

                  Michael

                  Comment

                  Previous template Next
                  Working...
                  X