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

Table Lookup

  • Filter
  • Time
  • Show
Clear All
new posts

    Table Lookup

    My typical table lookup (via field rules) consists of an ID# (linking primary idx)in column one and an item, unit, etc. in column two.
    I display only the item and fill the ID#. How can I display the item name in lieu of or in addition to the item number. I don't really want to include every lookup table in a set to have access to all the fields. Is there a way to assign column(2).value to a variable so I can display it along side the ID#?

    RE: Table Lookup

    Hello Terry,

    Not really sure I understand what you are asking. In a lookup, you can display any field in the lookup table, regardless of whether it will be use to fill in a field in the current table. If you want to display something that is not shown in the lookup table, the only way I know of doing this would be to built your own lookup using an array.

    Good luck,


      RE: Table Lookup

      Hi Terry:

      Like Jim, I too am not sure what you're asking but....

      The field rule lookup utility has a 'fill' and a 'show' column. Either can be left blank. Can't that get what you want?



        RE: Table Lookup

        Sorry for the confusion. I understand the field rule side of display/fill table lookup. The information I want to show after the the lookup has completed its task is the user informative text description of an item, not the id actually saved to the table bound to the form.

        field fill display
        id id no
        item yes

        After the user selects the item from the lookup table, the id is placed into the field and the item description is gone. The item description is a field only in the lookup table. Can I save the item description to a variable to display on the form so the user can still see it.

        Rather than add the description field a second time to the original table and defeat the purpose of relational....
        or create a set to allow the field to display with it's id,
        It seems that there should be some way to reference and save the second (or any) column of the lookup table to a variable.

        Do I have to change the lookup source to an array to do this?


          RE: Table Lookup


          If you're working on a form and entering that ID into a browse on the form, the in edit mode just drag the description from the field list to a spot on the form.

          If, the ID field is in the browse with no description, that new field will display the description for each ID in the browse as the pointer is moved from record to record.

          Is that what you want. No need to use a variable for that.



            RE: Table Lookup


            Having saved the id into the current table, you now want to be able to view related fields from the lookup table, based on a matching id, as you scroll through the current table. Right?

            You have two choices, so far as I know:

            1) store all the desired fields in the current table, and fill in those fields when the lookup is done...


            2) add the lookup table to your set, linked by id, using a one to one link

            -- tom


              RE: Table Lookup

              The third option would be to define some calculated fields on the form using the lookupc etc functions


                RE: Table Lookup


                Help -
                I don�t want to hijack, or whatever, this thread; but I have the same, I think, problem. I�m posting a new subject on mine now:


                  RE: Table Lookup


                  Help -
                  I don�t want to hijack, or whatever, this thread; but I have the same, I think, problem. I�m posting a new subject on mine now: