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

Invalid report filter on child table

  • Filter
  • Time
  • Show
Clear All
new posts

  • Invalid report filter on child table

    Can't seem to get to the bottom of this. I have a set shown in attachment. Have built a new report based on this with a few fields from transaction (parent) table in Detail section. Nothing else. Filtering works on fields in Project child table (1st child), but I get the error on other child tables when doing

    preview_report("txn_test_filter","Division->number = '400'") 'gets error

    preview_report("txn_test_filter","Project->number = '00019'") 'works correctly

    Paste any filter directly into report selection criteria of report and it works fine.

    So... rebuilt the set with Project as second child and now get the error when filtering on project, but no error on first child table. Again, paste filter directly into the report and it works fine.

    What's up?


    Oh, and if I create a form with a button to do the same thing as a query, it works fine.
    Attached Files
    Last edited by Bill Parker; 04-06-2013, 01:56 PM.

  • #2
    Re: Invalid report filter on child table

    Hi Bill.

    If you're trying to flatten the set shouldn't the Division table be a grandchild, linked 1:1 to Project?


    • #3
      Re: Invalid report filter on child table

      Tom, due to the evolution of the application, project and division are independent, although functionally they are now a hierarchy. So the structure is accurate.


      • #4
        Re: Invalid report filter on child table

        I submitted a bug report. I get same problem in Alpha Sports, but it works in v9.


        • #5
          Re: Invalid report filter on child table


          There is a (I don't know how) new report design parameter named Optimize Report, under the menu item Report. It is turned on by default. When it is on Alpha prunes any tables from the set that are not referenced in the report. This should speed rendering on complex sets.

          My filter referenced a field not displayed on the report. That explains why the filter worked when specified in Report Selection criteria (it was part of the report), and failed when passed in via preview_report() (it was not part of the report). Turning off Optimize Report solved the problem.

          Thanks to Cian for looking at this and taking the time to explain it. I could not find anything in the wiki.



          • #6
            Re: Invalid report filter on child table

            Hi Bill,
            Did you try placing that field on the report and hiding it? I am just curious how that would have worked with the Optimize feature on. But I am guessing you are using the same report with different filters when called, so that might not serve too well in practice?

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


            • #7
              Re: Invalid report filter on child table

              Yes, that would have worked, but does not fit my situation. Users get a dialog of filter parameters they can select. That covers 99% of cases. But there is also a button that lets tham access the full query genie to add more to the filter. In that case I have no idea what will be picked. The full filter prints on the report with an extra notice that there is special filtering.

              Cian is going to see if he can adjust the set prunung in a case like this where the filter includes a table that is not in the layout.



              • #8
                Re: Invalid report filter on child table

                Another good reason to keep my v11 trial...

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford