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

Report record selection filter not sensing marked

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

    Report record selection filter not sensing marked

    Hi there,

    I have a problem in printing a report which has a filter to print only marked records.

    I attach the db

    To get to my problem

    1. Debtors Selection Form displays on loading
    2. Select Enquire Accounts - 6
    3. Name Search enter Dave DAVE MILLER MOTORS is selected.
    4. If no transactions display, select Profile button. OK the Dialog box
    5. 5 Transactions should display.
    6. Activate Print Button.
    7. Select Preview
    8. There are no pages in layout is the result.

    Select Control Panel / Reports / Debt_Xsacts_by_Acc_Batch
    Design / Report / Select Records will display my filtering.

    (The layout of this selection box suggests that it should be all Trade_Transaction Records, with Marked button active. I am not able to get it working this way either

    Any ideas ?

    Looking forward
    Dave Mac

    It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

    #2
    Re: Report record selection filter not sensing marked

    Dave, your report is based on a set of tables. The filter you're applying pertains only to one of the child tables. Depending upon what you need in the app you're either going to have to base the report on a set in which "Trade Transactions" table is primary, or you're going to have to change the filter expression to use either a crosslevel filter or to flatten the query with flattenquery(). As it stands right now nothing in the filter tells the report engine which DEBT table record to use.

    Comment


      #3
      Re: Report record selection filter not sensing marked

      Hi Tom,

      Thanks for the help.

      As a test I have marked the parent record to filter the req record.

      I have managed to get something going using flattenquery(). I am using a test condition on the Trade_transaction.net_amnt as you can see from the attached db. Still unable to filter marked child records which is what I had in mind. Any way of doing this ?

      I wonder whether I am going about this the correct way ? Most systems have the need to filter / print parent / child records. How is it normally done ?
      Dave Mac

      It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

      Comment


        #4
        Re: Report record selection filter not sensing marked

        Most systems have the need to filter / print parent / child records. How is it normally done ?
        Sorry. The generality of this prevents a meaningful answer in the available time.

        In your app, why are you marking child table records, and then using the marks as a way of including those child table records in the report? If you're marking all the child table records that are linked to a specific parent record you can stop. There's no reason to mark the children. The only reason to mark them is if you wish to EXCLUDE some of the linked child table records from your report. Is that what you need? Or are you simply trying to print all the linked child records for a specific parent?

        Comment


          #5
          Re: Report record selection filter not sensing marked

          OK Dave here goes.
          I don't like using mark() as a tool for marking records for filtering. It can create havoc in a network environment and filters are somewhat difficult to get working properly. That being said, I see that you have used mark() fairly extensively. I changed it to get it to work... at least for what I believe you were asking for.

          I added a field "mark_f;c;1" to the trade transactions table, commented out line 51 and 58 of the Debt_Enq_OnFetch script and replaced td_xcts1.mark() with td_xcts1.mark_f = "x" and changed the base filter on the Debtors Enquiries form for the child table to be trade_transactions->mark_f = "x". The 5 records that get shown because they are tagged by the filters and actions of your Debt_Enq_OnFetch script contain these values in the trade transactions table field "net_amnt".
          -152.69
          225.30
          25.07
          24.57
          82.65
          None of these records have a value > 1000.00, which is what the filter expression on the Debt_Xsact_by_Acc_batch report is set to for which you are asking to show these records. I changed this report filter to use a global variable vgn_net_amnt with:
          Code:
          trade_transactions->net_amnt > var->vgn_net_amnt .and. Trade_Transactions->Mark_F = "x"
          and changed the radio button from "marked" to "all".

          I added an in-line xbasic action on the form print button with ui_get_number() to collect the value for the global variable vgn_net_amnt to pass to the report filter. With these changes, I believe the "tagged" (mark_f ="x") child records with values in the field net_amnt which are presented comply with the ask value and the desired report filter. I also added the net_amnt field to the report so you could see the field values of the presented records to confirm the values comply with the ask value delivered to the filter.

          While I believe this filtering of child records is what you want, I claim zero understanding of what this is all about. I hope this helped.
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: Report record selection filter not sensing marked

            Thanks for you input Guys

            Originally posted by Mike Wilson View Post
            OK Dave here goes.

            While I believe this filtering of child records is what you want, I claim zero understanding of what this is all about. I hope this helped.
            Certainly did help. Direction like this to see how it should be structured is worth its weight in gold.

            The purpose of all this is to achieve a quick display. In my ignorance i decided to include the following in my child table Trade_Transaction filter

            Trans_Type "CRN"
            .OR.
            Outstand_Amnt 0
            .OR.
            Date >= Var->gd_past1


            I attach the resulting db. This is on a db with approx 3,000 records in child table Trade_Transaction. When one has more than 100,000 records it takes forever to chew through. The solution to tag an additional field works.

            Thanks again
            Dave Mac

            It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

            Comment

            Working...
            X