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

Report showing repeated info. How do you fix this?

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

  • Report showing repeated info. How do you fix this?

    Greetings,

    I am having a problem when creating a report using the style set to tabular. I used the quick report genie, but the info keeps repeating itself on the report (see attached JPG image) when using print preview.

    I have also attached the ZIP file of the application so you may see what I am experiencing.

    I thought the genie would set things correctly? I guess not. What do I need to do to correct this? I thank you for your help.

    Regards,

    Pat

  • #2
    Re: Report showing repeated info. How do you fix this?

    Pat, I haven't had a chance to look at your zip, but this is almost always the result of mishandling the fields from the parent table in a set based report. If your report is based on a one-to-many set you need to insert a group break to "separate" the parent table records from each other. This makes it possible to "group" the related child table records together. Put fields from the parent table in the group header. Put fields from the one-to-many child table in the details band. This is explained in the User Guide chapter on Reports. Look for the section on Designing Reports for One-To-Many sets. Let us know how things go.

    Later on ...

    Pat, here's an example for you. Look for the report called Toms_rpt. It's based on Toms_set. In your original set you specified three tables in a parent, child, grandchild relationship. In that scenario the grandchildren should link to specific children.... not to the parent. So, if you study my set you'll see that I've given each cat an id, and used that to link to the fee payments. This makes it possible to show the fees charged per cat, which your original design could not do.

    Notice also that to prevent "repeating" field values in the report I had to use two group breaks with a three table set. Breaking clients, then breaking cats. (Pls don't report me to PETA). Hope this makes sense. Write back if you have questions.
    Last edited by Tom Cone Jr; 04-02-2010, 08:09 AM.

    Comment


    • #3
      Re: Report showing repeated info. How do you fix this?

      Hi Pat,

      Just as Tom suggested, insert Groups.

      As you have a 1:N grandchild table you need two goups.

      Please see attached, is this what you wanted?
      Last edited by Keith Hubert; 04-02-2010, 08:30 AM. Reason: Tom submitted sample first!!!!!
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


      • #4
        Re: Report showing repeated info. How do you fix this?

        Or, in some cases simply grouping won't solve the problem. In those cases it's usually because you are using a set that is too complicated for the report you are creating. More specifically, the set may have some 1-to-Many links that aren't needed to generate the report. Every 1:M link will generate another detail record.

        The general rule is to use the smallest set necessary when generating reports. If that means creating a special set for just one report, so be it.

        Comment


        • #5
          Re: Report showing repeated info. How do you fix this?

          Hi Tom,

          I thank you for explaining this to me, and for the example you have provided. That helped me out a lot to understand it better.

          My next question is how many fields can I create in a child table that I could safely use one group header for a report when using a one-to-many set (parent/child) with no grandchild table being used?

          Again, thank you as I look forward to your response.

          Regards,

          Pat



          Originally posted by Tom Cone Jr View Post
          Pat, I haven't had a chance to look at your zip, but this is almost always the result of mishandling the fields from the parent table in a set based report. If your report is based on a one-to-many set you need to insert a group break to "separate" the parent table records from each other. This makes it possible to "group" the related child table records together. Put fields from the parent table in the group header. Put fields from the one-to-many child table in the details band. This is explained in the User Guide chapter on Reports. Look for the section on Designing Reports for One-To-Many sets. Let us know how things go.

          Later on ...

          Pat, here's an example for you. Look for the report called Toms_rpt. It's based on Toms_set. In your original set you specified three tables in a parent, child, grandchild relationship. In that scenario the grandchildren should link to specific children.... not to the parent. So, if you study my set you'll see that I've given each cat an id, and used that to link to the fee payments. This makes it possible to show the fees charged per cat, which your original design could not do.

          Notice also that to prevent "repeating" field values in the report I had to use two group breaks with a three table set. Breaking clients, then breaking cats. (Pls don't report me to PETA). Hope this makes sense. Write back if you have questions.

          Comment


          • #6
            Re: Report showing repeated info. How do you fix this?

            Hi Keith,

            I thank you for your help as well. From looking at your PDF that is what I was trying to accomplish. Again, thank you.

            Regards,

            Pat



            Originally posted by Keith Hubert View Post
            Hi Pat,

            Just as Tom suggested, insert Groups.

            As you have a 1:N grandchild table you need two goups.

            Please see attached, is this what you wanted?

            Comment


            • #7
              Re: Report showing repeated info. How do you fix this?

              Pat, because there's no relationship between the number of fields in a child table and the choice of a group break field in a two table set I don't understand your question, sorry.

              Comment


              • #8
                Re: Report showing repeated info. How do you fix this?

                Hi Pat,
                how many fields can I create in a child table that I could safely use one group header for a report when using a one-to-many set (parent/child) with no grandchild table being used?
                I'm assuming that you are asking about joining fields to create an expression that would be the value to start records in in the next group?

                Because it is an expression you can make it as complex as you need.

                But remember the golden rule, KISS.
                Regards
                Keith Hubert
                Alpha Guild Member
                London.
                KHDB Management Systems
                Skype = keith.hubert


                For your day-to-day Needs, you Need an Alpha Database!

                Comment


                • #9
                  Re: Report showing repeated info. How do you fix this?

                  Hi Tom,

                  Thanks for getting back to me. What I wanted to know is that if I have all the needed info within a single table that has about 96 fields in it, would I be OK to create a report that utilizes only 8 fields from the 96 fields just from that same table? No sets involved, just a single table.

                  Again, thank you for your help.

                  Regards,

                  Pat


                  Originally posted by Tom Cone Jr View Post
                  Pat, because there's no relationship between the number of fields in a child table and the choice of a group break field in a two table set I don't understand your question, sorry.

                  Comment


                  • #10
                    Re: Report showing repeated info. How do you fix this?

                    Hi Keith,

                    Thank you. The KISS method always works, and now back to the news... :) Again, thank you.

                    Regards,

                    Pat



                    Originally posted by Keith Hubert View Post
                    Hi Pat,I'm assuming that you are asking about joining fields to create an expression that would be the value to start records in in the next group?

                    Because it is an expression you can make it as complex as you need.

                    But remember the golden rule, KISS.

                    Comment


                    • #11
                      Re: Report showing repeated info. How do you fix this?

                      Hi, Pat. Yes. The "unused" fields would not be a problem.

                      Comment


                      • #12
                        Re: Report showing repeated info. How do you fix this?

                        Hi Tom,

                        Thank you again. I hope it's OK to ask you this following question. How do you create a quarterly and yearly report using dates?

                        Regards,

                        Pat



                        Originally posted by Tom Cone Jr View Post
                        Hi, Pat. Yes. The "unused" fields would not be a problem.

                        Comment


                        • #13
                          Re: Report showing repeated info. How do you fix this?

                          Pat, actually it's considered bad form by many. Why? Well, if each message "thread" deals with a single question the message board can become a knowledge base, instead of a blog. People with similar problems won't have to read through all the earlier messages to get to your quarterly and yearly report question and answers, if they found this thread while searching "quarterly", if you see what I mean. So, please start a new thread, supplying the information needed to support it without refering folks back to this one. ok?

                          Comment


                          • #14
                            Re: Report showing repeated info. How do you fix this?

                            Hi Tom,

                            Sorry about that and I thank you for letting me know. I just posted the question on a new thread.

                            Regards,

                            Pat



                            Originally posted by Tom Cone Jr View Post
                            Pat, actually it's considered bad form by many. Why? Well, if each message "thread" deals with a single question the message board can become a knowledge base, instead of a blog. People with similar problems won't have to read through all the earlier messages to get to your quarterly and yearly report question and answers, if they found this thread while searching "quarterly", if you see what I mean. So, please start a new thread, supplying the information needed to support it without refering folks back to this one. ok?

                            Comment

                            Working...
                            X