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

Three-field Selection/View/Filter/Grid puzzle

  • Filter
  • Time
  • Show
Clear All
new posts

  • Three-field Selection/View/Filter/Grid puzzle

    I've spent over a day playing with this on paper...

    In the SQL world, I think this is feasible with some convoluted joins, unions, select ins, select distincts, etc. But can someone explain how I might achieve my goal in this WAS application?

    Table looks fundamentally like this: (if preferable, this could be structured as a view, with linking tables - but I fared no better with that approach)

    (3 fields)

    x y z <--- column names

    1 A !
    1 A #
    1 B !
    2 A $
    3 B %
    4 C #
    4 D #
    5 E $
    6 C #

    I wish to display a grid containing only DISTINCT column y filtered primarily on column z. The actual arguments available to the select/filter process are both x and z. All distinct y for any submitted z should be displayed, however, a special display attribute should indicate where there is also a match on x. Therefore, a match on x is optional, but where there is a match, it must be somehow reflected in the display. (Each displayed y will be a link to a detail view of y.) A few examples:

    GenerateGrid(x=1, z="#")
    desired result:

    **A** (asterisks, or some other visual attribute indicating a match on x)
    C (notice C is displayed only once, though it matches on both x=4 and x=6)

    GenerateGrid(x=1, z="$")
    desired result: (no match on x, so no special attribute)


    GenerateGrid(x=5, z="$")
    desired result:


    The first/biggest problem I've run in to is display of duplicate matches (as in first example). While there's an option for Unique Records Only, it seems inapplicable due to apparent necessity of including other columns in the filter/view.

    Or is this best solved via xbasic code? Any hints on how to implement that?

    [edit: I'm using standard .dbf for this; maybe an SQL db is the "no-brainer" answer?]
    Last edited by fsi; 07-07-2009, 10:03 AM.

  • #2
    Re: Three-field Selection/View/Filter/Grid puzzle

    Having received no response offering a solution for native .dbf, I worked out the following for standard SQL (in case anybody else has need).

    This is the verbose version (prior to elimination of WHERE in favor of JOIN). The _x_ tables are the linking tables, ARG1 and ARG2 are the "x" and "z" in the original post.

    select tblA.ID, 1
    from tblB, tblB_x_tblA, tblA, tblA_x_tblC, tblC
    where tblB.pkey = tblB_x_tblA.tblB_ID
    and tblB_x_tblA.tblA_ID = tblA.pkey
    and tblA.pkey = tblA_x_tblC.tblA_ID
    and = tblC.pkey
    and tblB.pkey = ARG1 and tblC.pkey = ARG2
    select tblA.ID, 0
    from tblA, tblA_x_tblC, tblC
    where tblA.pkey = tblA_x_tblC.tblA_ID
    and tblA_x_tblC.ID = tblC.pkey
    AND tblC.pkey = ARG2
    and tblA.ID not in
    (select tblA.ID
    from tblB, tblB_x_tblA, tblA, tblA_x_tblC, tblC
    where tblB.pkey = tblB_x_tblA.tblB_ID
    and tblB_x_tblA.tblA_ID = tblA.pkey
    and tblA.pkey = tblA_x_tblC.tblA_ID
    and = tblC.pkey
    and tblB.pkey = ARG1 and tblC.pkey = ARG2)

    Two columns are returned, the actual result (A-E, as in initial post), together with a second column consisting of either 0 (inexact match) or 1 (exact match). Duplicates are prevented.
    Last edited by fsi; 07-12-2009, 11:34 AM.