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

Issue designing report

  • Filter
  • Time
  • Show
Clear All
new posts

    Issue designing report

    I've almost completed converting an Alpha Four app to Alpha Five. I'm down to one final summary report. This report was initially created in Quick Basic because the developer could find no way to produce it in Alpha Four. I seem to be having the same issue in Alpha Five. Essentially there are three parts on the report: a summary of various billable transaction types identified by a two-character code; a summary of non-billable (maintenance) items of which there are only four; a late-charge detail of varying size. The simplest method I came up with has all the transactions in one table and a report consisting of a single detail section for the first section and two sub-reports for the other two sections. The first two sections work just fine but the third (second sub-report) comes up empty. I finally found the reason to be the initial section filters all transactions except "LD" (late-charge detail). In the second sub-report when I try to filter on only "LD" transactions it doesn't find any ... because they were excluded in the main part of the report.

    I subsequently created a "summary" set and added two more extract tables: one for the maintenance items and one for the late-charge detail. I fudged the invoice types in the linked tables to match the type of a single summary record in the primary table. It doesn't matter which, the idea was that when the report found the type in the primary table it would pick up the matching items in the linked tables for the sub-report sections. Voila. I have three sections exactly as I wanted except ... in the first summary section I now have a summary item for each detail item in the linked tables!!

    I've attached a zip file with the set (and hopefully the report (layout?) based on the set), a PDF of the old Alpha Four report and a PDF of what I'm now getting with my last attempt in Alpha Five. I've been working on this for five days and it's driving me nuts. Any thoughts?
    Attached Files

    Re: Issue designing report

    Not sure I understand completely but the subreports are generally placed in the detail section. When I made a separate version of your report and moved them there I think I see numbers more like your original report.


    Creating Sub-Reports

    A sub-report is an entire report that is placed in the Detail area of another report. Its main purpose is to display data from tables linked in a set using one-to-many links at the same level. A common example of this is a set used to track Charges and Payments on an account.
    There can be only one.


      Re: Issue designing report

      Stan, I moved the sub-reports up to the detail section as you suggested however I see no difference in the preview of the report. Perhaps you could attach the results of your changes and I could try to duplicate.


        Re: Issue designing report

        I thought I'd take a moment to close out this thread. I reached a solution however it took some creative effort. Essentially the report I was trying to duplicate had three sections: a billable transaction summary; a maintenance flight summary; and a late charge detail. Rather than using a three-table set, I modified the Xbasic billing code to create a single table (xtrSummary) with three "Report Sections" (RS1, RS2 and RS3). I then created a report using the report sections as the primary group and color equations to hide/display certain print values where and when needed.

        I couldn't come up with any way to duplicate the "Accounts "Rcvble/Paybable" values in the transaction summary (RS1). I kept getting calculated field errors of one sort or another. I ended up saving the values in global variables and used them in the last section of the report to produce the results needed. The attached zip file contains the final results.
        Attached Files