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

Cascading Lookup

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

  • Cascading Lookup

    I have a cascading lookup that finds a person based on what group they are enrolled in.

    The problem is that it only finds the people that are not enrolled in another group, since it finds the "first match" (see expression below).

    lookupc("f",Person_Id,"Group_id","[PathAlias.ADB_Path]/tbl_group_assign","Person_Id")=?

    Is there are way to write the lookup so that the it will find a person in more than one group?

    Hope that makes sense.

    Thanks much.

    Alex Steinman

  • #2
    Re: Cascading Lookup

    Do you mean you want to determine who is enrolled in more than one group? I am nor sure what this (what you describe) has to do with cascading lookups, surely if you search by group then it lists all people in that group? Have you tried the cascading lookups examples that are in the WAS samples?

    Comment


    • #3
      Re: Cascading Lookup

      Andrea,

      Thanks for the reply. Sorry for the miscommunication on my part.

      I'm not interested in determining who is enrolled in more than one group. I just want the user to be able to select the group from a drop down, which filters the list of people in the drop down below it, so that all the members of the group appear.

      For some reason, the lookup isn't finding all of the people in the group - just the people that are only in that group. If the person is enrolled in another group, they don't appear in the list.

      I assumed this was because the lookupc is only finding the first occurrence of the personID in the group_assign table.

      Does that make more sense?

      Thanks for any suggestions.

      Alex

      Comment


      • #4
        Re: Cascading Lookup

        Originally posted by steinmanal View Post
        I assumed this was because the lookupc is only finding the first occurrence of the personID in the group_assign table.
        That makes sense - I mostly work with SQL databases but have a look at the WAS samples for cascading lookups: http://afas.alphasoftware.com/Sample...okup.a5w#notes

        Lookupc seems a strange way of doing a filter - such lookups are usually more for 1-1 matches not for listing multiple records.

        Comment


        • #5
          Re: Cascading Lookup

          Thanks, again, Andrea.

          The reason for the lookupc is that it is a slightly more complicated filter - involving three tables.

          The workaround for now is to use the last record, instead of the first, but it isn't ideal.

          Hopefully, I can figure out another function that will work.

          Thanks, again.

          Alex

          Comment


          • #6
            Re: Cascading Lookup

            Originally posted by steinmanal View Post
            Thanks, again, Andrea.

            The reason for the lookupc is that it is a slightly more complicated filter - involving three tables.

            The workaround for now is to use the last record, instead of the first, but it isn't ideal.

            Hopefully, I can figure out another function that will work.

            Thanks, again.

            Alex
            Hm... I am used to SQL tables so a view would be my solution...

            Although "external record content get" or something akin to that seems more suitable for pulling more than one record up..

            Comment

            Working...
            X