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

Lookup Tables- Dependent Lookup

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

    Lookup Tables- Dependent Lookup

    I am new to Alpha.
    Primary Table: BoatList
    -two fields same as secondary lookup.
    Secondary Lookup Table: Boat-category-type
    Id Category Type
    001 Sail Sloop
    002 Sail Yawl
    003 Sail Catboat
    004 Power Console
    005 Power Cruiser

    In Default Form Primary Table "Boatlist" I have the lookups working but they are not logically connected. Dependent on what has been selected in Category, I
    want only the relevant "types" shown and available.
    If the user changes the "Category" field I want the "type" field to be cleared.

    In Table "Boatlist" in the Field Rules view, on field "type" at the "Lookup" Tab, under "Filters" I have tried this formula to supress display of the non-relevant records in the "Boat-category-type" Table, under filter

    Category=CURRENT(Category)

    This does not seem to work. Is this function only for "printing". Only one item comes up in the lookup. Any suggestions? How do I clear second field when user changes first?

    Also is this going to translate to a Web database ok?

    Thanks, Rick

    #2
    Re: Lookup Tables- Dependent Lookup

    Hi Rick,

    Welcome to the world of Alpha.

    What you need here is a Filtered Lookup. This has been asked before and there are many examples on this forum. Some may be in older versions but will still work in V9. Have a good search, reading what was asked and answered will be of great value to you. There will also be some examples for you to download and see what has been suggested.

    Also is this going to translate to a Web database ok?
    I'm afraid not. For the web components that will be whole new ball game, but the logic will stand you in good stead.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Lookup Tables- Dependent Lookup

      Rick,

      You were close. I think it should be
      Code:
      Category = Boatlist->Category
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Re: Lookup Tables- Dependent Lookup

        Tim your suggestion seems to work, thank you. I guess the current function is used for printing. -After changing the first field (Category), the second lookup now shows the right choices (after several tries). I am wondering why it seems to take several tries to be showing the reduced list boat "types" of that relate to the selection of the first list boat "category" - sail, power, paddle or row.

        Rick

        Comment


          #5
          Re: Lookup Tables- Dependent Lookup

          I think the problem is, if you go back to the boat "category" field and select some other value, the field "type" value still remains and is incorrect.

          Therefore when the "category" field is not empty, and someone selects a different value for "category", the field "type" value needs to become "blank" or to reset. Or possibly to automatically popup "blank" for selection with the correct values.

          I am wondering how I accomplish this. I am going to do some more searches on filter lookup.

          Th

          Comment


            #6
            Re: Lookup Tables- Dependent Lookup

            You could do this at the form level or table level in the field rule record events.
            At the form level use the Onchange event of the control holding the Category and use it to set the value of the second control to blank or ""

            This can be done with xbasic or action scripting - category field, action - Set field value
            Tim Kiebert
            Eagle Creek Citrus
            A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

            Comment


              #7
              Re: Lookup Tables- Dependent Lookup

              Thanks again. This is interesting. There seems to be many ways to accomplish things and being new to it, I have no understanding of the ramifications. Alpha is going to be a black box that you try things against for awhile, I guess. I think I am going to go look at Alpha Sports really hard.

              Comment

              Working...
              X