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

Subreport - problem with spurious child records

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

    Subreport - problem with spurious child records

    Thanks in advance for your time. Latest version 10.
    I created a report from a set - the set incorporates child records that appear properly. When printing the child records in a subreport, however, the formatting or something causes the child records to create spurious extra records, duplicating the last 2 or 3 printed.

    This always occurs about the 5th instance of the main records, and will appear continuously thruout the report every 4 or 5 main records. If only 1 child record appears the spurious records moves to every 10th record. So it has something to do with how the records are formatted or something in the subreport.

    The data easily fits in the subreport; the can shrink/etc has no effect, I've redone the subreport a dozen times and it is very consistent in the appearance of the spurious records.

    Barring a simple fix, can I exit a subreport based on some conditional criteria? I really don't know any other way to fix this as I think it is just a bug in the program.

    #2
    Re: Subreport - problem with spurious child records

    Originally posted by skumber View Post
    Thanks in advance for your time. Latest version 10.
    I created a report from a set - the set incorporates child records that appear properly. When printing the child records in a subreport, however, the formatting or something causes the child records to create spurious extra records, duplicating the last 2 or 3 printed.

    This always occurs about the 5th instance of the main records, and will appear continuously thruout the report every 4 or 5 main records. If only 1 child record appears the spurious records moves to every 10th record. So it has something to do with how the records are formatted or something in the subreport.

    The data easily fits in the subreport; the can shrink/etc has no effect, I've redone the subreport a dozen times and it is very consistent in the appearance of the spurious records.

    Barring a simple fix, can I exit a subreport based on some conditional criteria? I really don't know any other way to fix this as I think it is just a bug in the program.
    Rob

    Are you using QReportBuilder, the report writer for QuickBooks, or is this an Alpha 5 v10 question?

    When building a sub-report, you should have a filter for the subreport that contains a 'scanning("table")' within it. Is that there or was it removed?

    Other than than quick idea, you may want to have an image to help explain you situation or better yet a sample of the report with test data, so it can be looked at.

    I'm really guessing that this is regarding a5 v10, since QRB isn't in v10 yet..
    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


      #3
      Re: Subreport - problem with spurious child records

      Yes it is the A5 a10? (I cannot keep track) report generator.
      I did not know the Qwhatever referred to Quickbooks.

      The subreport uses the table selection (above the filter) and then parses the proper child records based on the set. I could not use a normal type set as the table has 5 child records for each parent; when I define the set I use "include parent even if no matching child". I print child records only if their amt >0.

      It seems to be the subreport print function; if I reverse the sort order of the report the spurious records always appear at the 4th or 5th parent record, then at every 4th or 5th after that. That's why my fixes were always playing with the length / width of the subr, the way the report handles it, etc.

      If I cannot figure out a way to exit the subreport, otherwise I could just exit when the amounts equal a bucket in the main database.

      Active link tables if that makes a difference.

      Thanks so much. Let me know if you need anything else...

      Comment


        #4
        Re: Subreport - problem with spurious child records

        repost in the a5v10 desktop forum.

        Not too many people troll here.

        Just us crazy ones..

        You'll be asked for the business explanation/purpose and some example data/database with what you've already done.

        We're just other users helping each other out, so help us to help you.

        Welcome to the Alpha world...

        You may want to check out some of the upcoming training at the IADN site. Click on the icon below.
        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

        Working...
        X