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
Devcon 2020 Goes Virtual! LEARN MORE >

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 Filter troubles

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Report Filter troubles

    Here is the filter I am using with 2 global variables that are set before calling the report:
    get_date = 01/01/2010
    tax_year = 12/31/2010

    Code:
    rep_filtr = "(datein <= Var->Tax_Year) .and. ( (dispdate={} .or. dispdate >= Var->get_date) .or. (dateout={} .or. dateout >= Var->get_date) ) "
    I am trying to show how many machines are in place as well as changes that affected machines not in place in the year being reviewed. In the screenshot below appears a record that should be eliminated by this filter since both its DISPDATE AND DATEOUT values were before 2010. In the report footer it shows the filter parsed the variable date values correctly. This is a one table report.
    Attached Files
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford
    Tags: None
    #2
    Re: Report Filter troubles

    I have a variable to select a field for the sort order. It seems that since MACHNO is not unique in all the records, that may be part of the problem. So I changed it to add ITEMNO if MACHNO is selected (MACHNO+ITEMNO). That did eliminate two records that sold in 2009, but I noticed that a few other machines that I actually do want on the list because they have not been sold but are out of service - should have been filtered out too because they were moved to the warehouse before 2010. The filter should be testing the DISPDATE before the DATEOUT I would think. Because these records do have blank DATEOUT fields. Perhaps I should use .AND. rather than .OR. when testing those two dates?

    A better way to write this filter would sure be appreciated!
    Robin

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

    Comment

      #3
      Re: Report Filter troubles

      Here is my logic & order for what the filter ought to test and find:

      1. All machines in place before the end of 2010:
      "DATEIN <= {12/31/2010} .AND. (DATEOUT = {} .OR. DISPDATE = {}) .OR.
      2. Only sales that occurred in 2010:
      (CASE(DISPTYPE = \"S\" .or. DISPTYPE = \"T\", DATEOUT >= {01/01/2010},
      3. Or disposals that occurred in 2010:
      DISPTYPE < \"S\" .OR. DISPTYPE > \"T\", DISPDATE >= {01/01/2010}}) .OR.
      4. Now add any other machines with a MACHNO still in the warehouse:
      left(MACHNO,1) = \"W\" )"

      So far this seems to work...
      Last edited by MoGrace; 08-29-2011, 08:20 PM.
      Robin

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

      Comment

        #4
        Re: Report Filter troubles

        Well I spoke too soon because when I reposted the table, this filter won't work and all the records are shown. Can't you use a case() or an if() statement in a query? Because some records have both a dispdate and a dateout value and so I need to test for the disptype value then select which field to test. I thought it might work better to query the table then print the report based on the current selection of records, but I can't get these records with both values to select the dateout value only.

        Some advice please!
        Robin

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

        Comment

          #5
          Re: Report Filter troubles

          You may have to be more explicit with your parentheses in the first and last sections.

          ("DATEIN <= {12/31/2010} .AND. (DATEOUT = {} .OR. DISPDATE = {})) .or.
          ........ .or.

          (left(MACHNO,1) = \"W\" ))"
          Last edited by Stan Mathews; 08-30-2011, 03:10 PM.
          There can be only one.

          Comment

            #6
            Re: Report Filter troubles

            Hi Stan,
            Yeah those parentheses are a killer! I figured out that to make a case() or if() type statement, this works substituting the actual dates with global variables set by the calling script:

            " (DISPTYPE = \"\") .OR.
            ( (DISPTYPE = \"S\" .OR. DISPTYPE = \"T\") .AND. (DATEOUT >= {01/01/2010}) ) .OR.
            ( (DISPTYPE < \"R\" .OR. DISPTYPE > \"T\") .AND. (DISPDATE >= {01/01/2010}) ) .AND.
            (DATEIN <= {12/31/2010}) .OR. (LEFT(MACHNO,1)=\"W\") "

            Since I can now test the Disptype flag, I don't have to test which date field is blank. Omitting the value R (Returned to service) includes it by default as an active machine, and any machines in the warehouse (W+Machno) are included regardless of the date put there. I added a new index for the Disposal table that is 1:N, so I can lookup more detail from the transaction table based on ITEMNO+DISPTYPE - And it only took me 3 days!

            This forum is a great place to store these notes...
            Last edited by MoGrace; 08-31-2011, 11:53 AM.
            Robin

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

            Comment

            Previous template Next
            Working...
            X