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

Conditional Table lookup

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

    Conditional Table lookup

    I would like to create a multiple capable conditional table lookup that would output a list of alphanumeric records from another table based on the previous fields value, i.e. field "make" = Dell would search another table called make_models for all Dell entries and provide a list for selection, i.e if field "make" = Compaq it would provide a list from the make_models table for all Compaq entries for selection. I also want the ability to add new records to the make_models tables or the parent table for new vendors.
    Tags: None
    #2
    RE: Conditional Table lookup

    I'm guessing that you have something like this:

    Orders table that includes field for the "make" of computer.

    Make_Models table that includes all the models for all the different manufacturers, with a field which I'll call "Manu" for clarity; and a field "Model" with model numbers.

    It seems that you should just do the lookup on "Make_Models" based on the filter "Manu" and the sort order "Model". You could then display the "Model" field, and fill it in on the Orders table.

    Is this what you were looking for?

    Stephen
    Stephen Pilon
    Associate Librarian
    Christendom College

    Comment

      #3
      RE: Conditional Table lookup

      Stephen thanks for replying,
      Your interpretation is correct except for its an inventory list, not that it matters. I am having trouble filtering more than one vendor in either a conditional lookup or lookup table for the "Manu" field to produce a list of models for that "Manu". I have tried an exercise in the A5V5 users guide for "selected lookup table records" that sets a global session variable on a table (page 123), but I don't understand a couple of the global session variables. What is the "Value" header and "Name" header, which one represents the table field and the "var->name". I have not found any help info for this option.

      Any help would be much appreciated.

      Comment

        #4
        RE: Conditional Table lookup

        Paul,

        I still a little confused. Can you describe the tables a bit more? How many are we dealing with? Are they in a set? What fields do they have in common?

        Stephen
        Stephen Pilon
        Associate Librarian
        Christendom College

        Comment

          #5
          RE: Conditional Table lookup

          Hi Paul,

          Have you looked at using field rules for a lookup. You can have a vendor table that is not attached to your current table. Through the use of field rules do a look up based on the vendor table.

          Then for the part numbers use a lookup for the part number and filter on the vendor name. Of course the part number table will need to have the vendo name in the table. And in that case you could do a look up of the vendor in the part number table as well.

          I think this will be a better way to go.

          Dan
          Dan

          Dan Blank builds Databases
          Skype: danblank

          Comment

            #6
            RE: Conditional Table lookup

            I have two tables one call "inventory" and one called "make-model", with alike fields in both tables being "make" and "model", while in a default browse on the "inventory" table I enter a name in the "make" field and then tab to the "model" field, at the "model" field I want only the list of models to drop down related to what I entered in the "make" field, if I enter Dell a list of only Dell models pop up if I enter Compaq in the "make" field only a list of Compaq models pop up, etc. I don't think I can use the "lookup field" option in the field rules on the "inventory" table to filter multiple models from different vendors? Do I need to create a "global session variable" on the "inventory" table, do I then have to create a script to enable the "global session variable" ?

            Comment

              #7
              RE: Conditional Table lookup

              Thanks for taking the time to reply to my question,

              I have two tables one call "inventory" and one called "make-model", with alike fields in both tables being "make" and "model", while in a default browse on the "inventory" table I enter a name in the "make" field and then tab to the "model" field, at the "model" field I want only the list of models to drop down related to what I entered in the "make" field, if I enter Dell a list of only Dell models pop up if I enter Compaq in the "make" field only a list of Compaq models pop up, etc. I don't think I can use the "lookup field" option in the field rules on the "inventory" table to filter multiple models from different vendors? Do I need to create a "global session variable" on the "inventory" table, do I then have to create a script to enable the "global session variable" ?

              Comment

                #8
                RE: Conditional Table lookup

                Hi Paul,

                Attached is a small example to help get you started. It isn't polished but it may help.

                Dan
                Dan

                Dan Blank builds Databases
                Skype: danblank

                Comment

                  #9
                  RE: Conditional Table lookup

                  Dan, thanks for the example and responding quickly, this is exactly what I am looking for! As you can see I am new to this. It was the filter I was stuggling with, I modified the table name in the filter for my test db and it works find.

                  Where can I get some more info on syntax for these types of expressions?

                  I also noticed that when I check "user can add records to lookup table" & "unique records only" that the default form only shows one record entry? Do you think this is a bug or am I miss understanding the function of "Field Rules" options.

                  Comment

                    #10
                    RE: Conditional Table lookup

                    Hi Paul,

                    To get more snipets of code, I'd recommend the PDF files that Alpha puts out. Here is a great place to start:

                    http://www.alphasoftware.com/support/appnotes.asp

                    Peter Wayne's book is a great place to continue learning. He also has a web site at www.learn alpha.com. Look at the articles, do some of the lessons, download the demos. It is a great place to learn and see examples of what other people have done.

                    On the Unique Record Check. That is what it means. In the example I sent you the make shows for each record. If you check the unique box, only one manufacturer will show. So instead of 3 Compaq's there will be only one. On the second look up don't check the unique box. It is not a bug, but doing as designed.

                    Play around with the example and you will begin to get the feel of field rules. Field rules are one (won) of the great things about A5.

                    Study the functions in A5 and before long you'll wonder how you got along without A5.

                    Dan
                    Dan

                    Dan Blank builds Databases
                    Skype: danblank

                    Comment

                    Previous template Next
                    Working...
                    X