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

Grid Filter - Ability to filter on a field that is not in the data source of the grid.

  • Filter
  • Time
  • Show
Clear All
new posts

    Grid Filter - Ability to filter on a field that is not in the data source of the grid.

    I have a use case where a client wants to see all pending estimates by week ending and division. This is very easy. I can use a summary SQL view or a detail view which is then grouped and summarized in the data source of the grid.
    The challenge is to filter the data by another column that is not part of the grid. There is a field called [ClosePercentage] which indicates the likelihood that the estimate will be approved. The use case is to now show all estimates with a closing percentage of 50 to 100%
    Since this column cannot be grouped, it is not visible or part of the available fields on the grid. In MS Access, I can do this easily by writing VBA to construct the where clause as needed.
    The question is how to add search fields that do not exist in the data source and customize the where clause to respect these new search fields.

    Here is the SQL query use case. Any ideas would be much appreciated. Perhaps embedding the grid on a UX and then simulating the search part with UX controls. Selwyn did a video for this but the search fields had to match with fields on the grid which is not helpful for my use case. me.

    The grid contains CloseWeekEnding, Division, EstCount, EstimatePrice, EstProfit and EstProfitPct

    , Count(DISTINCT EstimateRevNo) AS EstCount
    , Sum(EstimatePrice) AS EstimatePrice
    , Sum(EstProfit) AS EstProfit
    , iif( sum(EstimatePrice) = 0 , 0, sum(EstProfit) / sum(EstimatePrice) ) AS EstProfitPct
    FROM Estimate.viwEstimatePendingDetail
    WHERE CloseWeekEnding >= '6/1/2021' AND ClosePercentage BETWEEN .5 AND 1
    GROUP BY CloseWeekEnding, Division

    Can you make the summary SQL include

    WHERE ClosePercentage BETWEEN .5 AND 1 .and......,rest of the selection criteria?
    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


      Yes, but the .5 and 1 need to be arguments. The client wants a choice to see "all" estimates or any range of closing percentages which can range from 10% to 100%.


        I would expect this can be accomplished completely within sql, and the way I see it, the only need for an argument would be to define the date range.
        If you could provide some sanitized data, it would make verifying the answer much easier. Another thing to improve the response is sql "flavor".

        Gregg is a great site to test and share sql code


          I was able to accomplish the goal by embedding a grid on a UX. I used the UX to replicate the look and feel of a grid search part. When I perform a search from the UX, I call an XBasic function to pass the filter arguments to session variables. I then execute {dialog.EmbeddedGrid_NWORDERSGRID}.showAll(); to refresh the grid. I modified the onSQLSelectQuery and onSQLCountQuery server-side to construct the where clause on columns that don't exist in the grid. It worked as expected. You have to use Live Preview since session variables don't work in Working Preview. I also learned that once you change the base SQL statement, you must handle everything including totals, pagination, etc. This does involve extra work but at least I can see this is now possible.

          It would be optimal if I can just change the filter so I can leverage Alpha to do everything else that it does inherently like record count, base SQL statement, pagination, totals etc. I checked OnSearchPartFilterCompute which works if you turn search part. The problem is I can't hide that section. I also don't know how to fire the OnSearchPartFilterCompute event from the UX. The {dialog.EmbeddedGrid_NWORDERSGRID}.showAll() does not trigger the OnSearchPartFilterCompute event.

          I will share my final solution using Northwind sample database.

          UX with an embedded grid. City is passed to session variable which becomes available in server-side events for the grid.


            Another idea would be to use the search button in the UX to create a temporary table in SQL, then base the grid on that.
            Pat Bremkamp
            MindKicks Consulting