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

Filter output

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

    Filter output

    Hello,
    I'm spinning my wheels on getting only specific values to show up on a report. I've build a report based on created estimates within Quickbooks. I'd like to only show items that have the word "labor" in the description. The problem here is that sometimes it's entered as "labor" and other times its "labor buildingA" or B or C etc. I tried using a filter

    ESTIMATELINEDESC = "LABOR*" (asterisk for wildcard)

    but this is not working.
    Tags: None
    #2
    Re: Filter output

    Either

    1. "LABOR" $ ESTIMATELINEDESC

    2. contains( ESTIMATELINEDESC,"LABOR") - case sensitive

    3. containsi( ESTIMATELINEDESC,"LABOR") - case insensitive


    will work

    Edit: Here is an image showing how to find functions. From the expression builder, press F4
    Last edited by Al Buchholz; 05-08-2008, 04:48 PM.
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment

      #3
      Re: Filter output

      This worked great! Thank you.

      Comment

        #4
        Re: Filter output

        I'm trying to compare labor from a purchase order against labor entered in customer estimate. I've added both tables to a report and have both fields filtered to only show LABOR. This report is grouped by customer to make it easier to read. My problem is that the purchase order may have two or three lines containing LABOR and the estimate has many more. When I run the report it lists all the labor lines from the estimate correctly but takes the first line from the purchase order (that is labelled as LABOR) and duplicates it down, matching the number of rows for labor in estimate. How can I list labor lines from purchase order within the same report? I tried going from a one-to-one connection to a one-to-many connection but that doesn't seem to fix it.

        Comment

          #5
          Re: Filter output

          From what I'm reading, you'll need to structure some thing like this diagram shown in the attached image.

          You'll also need to use two sub-reports - one for the line tables.

          That will show the lines of the estimate and the po next to each other.

          If you want to only compare the summary of the labor in the estimate vs the labor in the po, you should summarize each first and then link to compare. But it sounds like you want the line detail...

          Hope that helps. It's a fairly complex idea at first, but simple once you use it.
          Al Buchholz
          Bookwood Systems, LTD
          Weekly QReportBuilder Webinars Thursday 1 pm CST

          Occam's Razor - KISS
          Normalize till it hurts - De-normalize till it works.
          Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
          When we triage a problem it is much easier to read sample systems than to read a mind.
          "Make it as simple as possible, but not simpler."
          Albert Einstein

          http://www.iadn.com/images/media/iadn_member.png

          Comment

            #6
            Re: Filter output

            Excellent. I was missing the piece to sub-reports. Once creating the sub-report, I was able to group them and make them look like they're related.

            I have another question.

            When running the report, can I have it ask the user for the company name from a list? Do I need to enter in each customers name as a choice? I'd like it to pull the name from the table field CUSTOMERREFFULLNAME. That way if we add a new customer, it automatically has it as a choice.

            Comment

              #7
              Re: Filter output

              Look at scripting - create an action script making a dialog box with a record list from the table. You can use that variable to filter the report with.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment

                #8
                Re: Filter output

                I was able to establish a list using the table. What do you mean by "You can use that variable to filter the report with." ?? Can you clarify please?

                Comment

                  #9
                  Re: Filter output

                  Originally posted by Emerald IT View Post
                  I was able to establish a list using the table. What do you mean by "You can use that variable to filter the report with." ?? Can you clarify please?
                  How did you establish the list? Did you use and xdialog box as I suggested? If so, then the xdialog has a variable that will contain the selected data and that variable can be used in the filter of the report.

                  See attached image.
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment

                  Previous template Next
                  Working...
                  X