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

Cascading Tables

  • Filter
  • Time
  • Show
Clear All
new posts

    Cascading Tables

    I see in the documentation that you can use cascading tables for a lookup, but can't figure out how to do that. Any suggestions?

    David A. Volgas, MD

    RE: Cascading Tables

    There are Cascading lookups , Table lookups and Conditional Table lookups

    Cascading lookups are simply lists of values that cascade

    i.e. in the Layout edit field typing


    would create top level of


    and under fruit (because of the leading '+') would put


    under vegetables would put


    The text is an outline format - you can add more levels by adding more leading
    '+' characters - does this answer your question?


      RE: Cascading Tables

      Actually, what I am trying to do is create a lookup based on a table which drills down through various fields in the table. For example

      a table has the following fields:
      Region Char 15
      AO Class Char 15
      AO Subtype Char 15
      Description Char 50

      What I'm trying to do is have a lookup which gives:

      Shoulder (Region)
      11A (AO Class)
      11A1 (AO subtype)
      Metaphyseal (simple) fracture (Description)


      The table may change on may be updated, so I don't want to hard code the tree.
      Does that make any sense? thanks for your help.

      Dave Volgas, MD
      David A. Volgas, MD


        RE: Cascading Tables

        I have used a Cascading list in a similar use. I used one field for Catagory, one for subcatagory and one for su-subcatagory. When you create the casacade list in field rules the a table can also be created assigning the data to each of the field noted. At the entry level you work from the final field, i.e. subcategory, choose the options you want and all three field fill.


          RE: Cascading Tables

          Thank you, bu I can't figure out how to use field 1 for the top level of the cascade, field 2 for he next level, etc.

          Any suggestions?
          David A. Volgas, MD


            RE: Cascading Tables

            Example: With three fields
            GO TO FIELD RULES
            Field1 is Data Entry
            Field2 is Data Entry
            Field3 is Lookup ( all the work is done at Field 3)
            Lookup Style is Casacade List
            Type your list
            (As you Type it you also create a Fill table)

            The Fill Table is Backwards with Field3 and it's data first.
            Field3 Field2 Field1
            White Tennis Shoes
            Black Tennis Shoes
            White Basketball shoes
            Black Basketball Shoes

            Remember all this is done at field rules for Field 3.
            Hope this helps.


              RE: Cascading Tables

              If you want a dynamically maintained cascade list (i.e. field1 is the top level, field2 is the intermeddiate, field3 is the lowest level) I can't do this yet, but I am getting closer. Currently it requires a5 version 5.0 - the changes involved to back-port this to version 4.5 are small, so maybe I can slip this into the next 4.5 patch (along with fixes to a couple compatibility problems folks are reporting - some causing crashes ).

              The snag I am running into (in version 5.0) - is that exclusive access to the table is needed to modify the field rules - this may be acceptable if the source of the lookup is modified infrequently. The other problem which needs to be fixed: I am running into an artificial limit on the size of the 'layout' string. If I fix the limit problem, and back-port the changes, then an xbasic script could be used to maintain the lookup info.

              The Xbasic to change a table's field rules on the fly involves use of the .rules_get() method - i.e.

              t = table.reset("",FILE_RW_SHARED)
              r = t.rules_get()
              ' start modifing the field rules via xbasic
              ' for a field
              cascade_list = ""
              ... build cr-lf list in cascade_list
              r.service.lookup.cascade_choices = cascade_list