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

Creating reports for sets

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

    Creating reports for sets

    I keep thinking that there should be an easy answer but I haven't found it.

    A3 to A4v6 have been very helpful over the years but when working with sets I've had to deal with repeated lines in browse tables and reports. Have learned to deal with [ignore] some & devised workarounds for some others. But it makes creating reports an ardous task. And exports are suspect.

    i.e. On a report [or browse table] the data in a parent record linked to multiple child records will be repeated for each child record. And in reports, the summary fields will total the multiple repeats of the parent entry.

    Most recently I had a browse table displaying, correctly, about a dozen lines. But when I printed it [to screen] I got about 30 or more repeats of each line!

    Please,what am I missing here? Have I provided enough info here? As it stands I have multiple fears of moving on to my new A5 program.

    #2
    RE: Creating reports for sets

    You need to insert a grouping level. Then, place the "browse" items in the Detail Section.

    The Parent database info should be placed in the Group header section. If you wish to place parent fields in the Detail Section, then specify them as uniqe. Otherwise, they're repeated for each detail item.

    gm

    Comment


      #3
      RE: Creating reports for sets

      Thanks,
      I think that I follow that. Will try it ASAP.
      Craig

      Comment


        #4
        RE: Creating reports for sets

        Okay, it took a while until I could try to rearrange a report layout.

        Regrouping does relieve the display duplications.
        But the problem erupts again when trying to
        summarize, seeking totals, comparisons and
        reconciliations. I'm back in the quicksand of duplications
        that are not easily visible.

        I have several databases where one transaction can affect
        multiple accounts. Using sets eases the entry process, but
        getting a meaningful report has been difficult. The main
        problem has been that the parent database feeds a
        duplicate of its data to match each child record.

        The only solution that I've found has been to create
        computed fields that reject duplications. But this nearly
        doubles the number fields needed. And takes hours of
        studying and conniving. To debug each glitch one must
        work through layer after layer. And the results are still
        suspect!

        Can't help feeling that there must be a better, simpler,
        way that I'm missing. Can y'all help?

        Thanks for your attention.
        Craig

        Comment


          #5
          RE: Creating reports for sets

          Craig,

          Have you tried using a Calc Field;
          VarAMOUNT=IF(SYSTEM-"CNTR_GRP1=1,AMOUNT,0)
          This will then only take the first value of the many records in the child if you set a group for the bunch of records you are concnerned with.
          The summary field will be VarAMOUNT, not AMOUNT
          Also you can avoid printing the redundant records with
          another calc field;
          PRINT IF(SYSTEM-"CNTR_GRP1=1,CHR(127),"") and set the format for this field to "-".
          Steve

          Comment


            #6
            RE: Creating reports for sets

            Steve,

            Boy,does that sound good! Gonna go try it now.

            Thanks a bunch.
            Craig

            Comment


              #7
              RE: Creating reports for sets

              Steve,

              Been checking it out. So far it looks good. Real good!

              Thanks for introducing me to page 12-23 in my dog eared A4V6 Manual. Somehow I had missed it all these years.

              In my cash journal I can now use:
              IF(SYSTEM-"CNTR_GRP1=1,DEP_AMT,0)
              IF(SYSTEM-"CNTR_GRP1=1,CHK_AMT,0)
              Etc,. etc.

              Again, thanks.

              Take care.
              Craig

              Comment


                #8
                RE: Creating reports for sets

                Craig,

                Everything is simple once you understand it!

                Glad I could help

                Steve

                Comment

                Working...
                X