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



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 grouping questions

  • Filter
  • Time
  • Show
Clear All
new posts

  • report grouping questions

    I am designing a billing statement report to print when a customer's balance due > $.10. Three people are listed on the salesform (owner, operator, applicator). The user chooses (via a radio button) which person is billed for this sale. The button choice fills in either "ow", "op", or "ap" in a field called "bill" on the salesheader table. I want the billing statement to total the amount owed on any number of salesforms by an individual, whether he be an ower, operator, or applicator.

    I had a simpler billing statement in the past where the owner was always billed. On the report, Group1=custid1, Group2=salesform no. The report summarized each ticket owed and gave a grand total.

    Now I'm not sure how to group or filter the statement so that all charges still print to an individual, whether he be custid1, custid2, or custid3. I have thought of a couple of solutions which involve table reconfiguration, but this needs to go out to 20 long-distance users (on Runtime) and I really don't want to deal with their data. Can someone think of a way to change the grouping/filtering on the report only to accomplish this?

  • #2
    RE: report grouping questions

    I would create a display calc field based on who is being billed. Assuming:

    Owner id is custid1
    Operator id is custid2
    Applicator id is custid3
    if for some reason user entering the salesform doesn't select someone to bill, bill the owner

    the calc field would look something like this


    Then I would add a group break on this calculated field.

    Hope this helps.


    • #3
      RE: report grouping questions


      I fear it's going to be more difficult. Wouldn't your approach 'bunch' (a technical term) all the 'op' records together, all the 'ow' together, and all the 'ap' together? I think Becky wants the group break on the customer name or id, and to include all records where this person is responsible for a bill, whether they happen to be an op, an ow, or an ap.


      you might investigate creating a temporary table, that can be thrown away after the report is run. In the temp table populate it by stepping through the real table, and copying over to the temp table one record for each responsible customer, regardless of whether they're an ow, an op, or an ap. Base your report on the temp table.

      -- tom

      -- tom


      • #4
        RE: report grouping questions

        The result of the calc field would be a customer id. Based upon who is paying, it would be the id of Owner, Operator, or Applicator. I did make another assumption; that there is only one id per person/address irregardless of how that person can be classified (ow, op, ap).

        In creating the group break, for 'break on change in' choose 'expression' and put this calculation in the expression builder.



        • #5
          RE: report grouping questions

          Forgot to add that this group break calculation would then 'bunch' the records on the calculated customer id, not by ow, op, ap.

          Attached is a small app showing how I did this.



          • #6
            RE: report grouping questions

            Shelly, yes, I see that now. However, I understood that any one customer might have several different records, in some of them the customer would be responsible as ow, in others the same customer would be responsible as ap, etc.

            Guess I'm off base, so I'll hush up.

            -- tom


            • #7
              RE: report grouping questions

              Thanks, Tom & Shelly, for your suggestions.

              Tom-I had already thought of a way I could use your method. I was just being lazy and wondered if there was a way I wasn't considering to modify my existing report.

              Shelly-I'll give your suggestion a try and see what happens. Thanks!


              • #8
                RE: report grouping questions

                Shelly-the calc field worked great and saved me a lot of effort on the release of an update disk. THANKS!!