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

Simple report problem

  • Filter
  • Time
  • Show
Clear All
new posts

  • Simple report problem

    I am attempting to print a travel agency invoice with cruise passsenger names listed. (Normally 2 to 4 names). The names are in a people table and attached to the reservation via a Pax table. The attached test-folder has all of the required tables, sets, report, etc to execute with a few entries in each table. I have tried sub-reports and filters with no success. I get all of the entries in the Pax table, not just those attached to the reservation via the index. My simple test has my notes inbedded. HELP HELP


  • #2
    RE: Simple report problem


    I haven't looked at your files, and I don't know what a PAX table might be. However, this sounds like a situation where you will be better off building a temporary table at print time, copying records there from both the passengers table and the PAX table. If you're connecting to the PAX table via ODBC it's possible the ODBC link doesn't support the queries you need to generate your report. Copying those records to a temporary Alpha Five table, and then linking that table into your report's set would overcome such a limitation.

    -- tom


    • #3
      RE: Simple report problem

      Pax is my name for a child table of keys that point to peoples names in my people table. I am not connecting via ODBC. If you get a chance to load my test-folder and look at the invoice set, you will see the linkage to Pax. The mode of operation for my users is to enter the information for a customer and then throught the use of a button, print the one invoice at that time. I am not sure that copying to other records is the best approach.



      • #4
        RE: Simple report problem


        I looked at your app for about 15 minutes, and while I did not solve your problem, I do have a suggestion which I think would help.

        Your two sets, master and invoice, are way to complex. I think you did it so you could put all the info on one form. Perhaps a better approach would be to split the sets into managable sizes and then use a main menu with appropriate buttons to open smaller sets.

        Hope this helps.

        Jay Talbott
        Jay Talbott
        Lexington, KY


        • #5
          RE: Simple report problem


          I wince whenever someone says they have a 'simple' report problem. Your invoices set has 15 tables in it, some of which are arranged 6 layers deep. I think Jay's idea of simplifying the set design is a good one. You might benefit from reviewing Dr. Wayne's experiences along these lines. Check his article 'Simplify Your Application' at www.learn There are real performance penalties from using complex sets, especially in multi-user networked settings.

          Your basic requirement in this report is to establish a group break on the reservation or invoice number. You could put the common information in the group header, and the traveler's names in the group details section. In your set, however, this arrangement doesn't work, and figuring out why would take, I fear, a great deal of time. My guess is that your link expressions in the set are getting in the way, or the fact that the people table is linked more than once is causing Alpha Five a problem. Simplifying the set should get you past the current hurdle.

          Good luck, and let us know how it turns out.

          -- tom


          • #6
            RE: Simple report problem

            Sorry, but I did not mean to infer a simple report. The simple that I was refering to was the test report that I put together to demonstrate the problem I am having. If you look at the master.set which is used for data entry, you will see the numerious child tables that are required to allow flexability to the system. My only problem with the report, is filtering out and printing only one time the children from the pax table that match the reservation parent. The link is the reservation-id in the reservation table and the reservation-id in the pax table. Currently, this is a single user system.



            • #7
              RE: Simple report problem


              Right. Instead of thinking of it as a query with a filter expression to find the right grandchild records, try nesting group breaks. Break first on the reservation_id, then break the reservation_id on people. -- tom