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

Subreports Bug

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

    Subreports Bug

    Hi All,

    Attached is a dummy test dbase showing a bug that is difficult to spot and shows in both V4.5 and V5.

    Can some better brains than mine think of a fix since I need this scenario in lots of situations. I see it has been discussed before with no obvious solution. (I have tried using conditional objects but this does not give me the required result)


    Michael

    #2
    RE: Subreports Bug

    Micheal,

    In the set definition for Payments, the link to both
    Due & Paid has

    Include record from Parent table: Always - even if no matching child record exists

    Change that to:
    Include record from Parent table: Only if a matching child record DOES exist

    and your "bug" is magically solved. :)

    Comment


      #3
      RE: Subreports Bug

      Melvin,

      Thanks for your tip, but your advice does not cure the bug, wish it would.

      I can filter the parent records no problem. I need a reliable link of child records. The report shows a parent with the correct 'Due' data but the 'Paid' from a completely different record. In my attachment, if you look at records with Link No's 15, 51 and 101 you can see the error.

      Michael

      Comment


        #4
        RE: Subreports Bug

        Michael

        AN ASSUMPTION!!

        It appears that the amounts due are being paid by instalments

        If so the in the Set the paid table should be linked 1 to many to the Due table.
        COLIN

        Comment


          #5
          RE: Subreports Bug

          On a second look I may well be wrong!!

          Comment


            #6
            RE: Subreports Bug

            Colin,

            If you check my attached dummy dbase, you will see that the set is Header"Due(one to may)"Paid(one to many. A very common structure. The problem is with the report.

            Michael

            Comment


              #7
              RE: Subreports Bug

              Michael
              there are no entries in Paid for 15 51 an 101.

              After making a paid entry for each Voila!

              No idea what the actual problem might be.

              Back to you

              Comment


                #8
                RE: Subreports Bug

                Hello Michael,

                I did not look at your attached example, but there is a known issue with subreports when there are at least two one-to-many child tables linked to the parent. If one of the child tables does not contain records, the other child records do not print in a subreport. I have found this intermitant and hard to pin down. Alpha has identified this problem and there is an unsupported fix, but there has not been a general patch released that addresses this issue (at least to my knowledge). You might drop Alan Buchholtz an email on this as he was the one who was able to consistantly demonstrate this to Alpha. Basically, I don't use subforms because of this issue. I have found a work around that has worked for me if you need to use subforms. If you put a meaningless sort order expression on the subforms, it prints all the records correctly, something like this:

                if(a_Field_Name = 1,1,1)

                Good luck,
                Jim

                Comment


                  #9
                  RE: Subreports Bug

                  Jim,

                  Thanks for the input. I had read up on your previous threads on this subject.

                  Your sugested fix of a dummy sort order does not fix my example. The parent still adopts the wrong child records under certain circumstances.

                  Since this report structure is a very basic/common scenario, I would hope Alpha had a fix for this because it occurs in V4.5 and V5 and possibly V6.

                  Michael

                  Comment


                    #10
                    RE: Subreports Bug

                    Hello Mike,

                    I took a look at your example, and although it may be the same underlying issue, this is certainly a different manifestation of it. Have you sent this example to Alpha as a bug report?

                    I issue I was speaking about has been addressed and fixed in v6.

                    You say you can get the functionality you desire with a conditional object. Why not?

                    Thanks,
                    Jim

                    Comment

                    Working...
                    X