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

Dynamically populate field choices.

  • Filter
  • Time
  • Show
Clear All
new posts

  • Dynamically populate field choices.

    Let's say I have a table with all customer information with many fields, including company, person_calling. I also have a different table with work order information based on which company calls in, including fields issue_count, company, and person_calling. In the table with all the customer information, the person_calling field is empty for all records. At the moment, a user can add an entry to the person_calling field in the work orders, but it's not associated with the company. So if there's a person "Mike" from ABC company, and a different "Mike" from XYZ company, you can really track which one work for which company.

    I have three tables.



    person calling

    On the work order form, based off the work_orders-customer set, when selecting the work_orders->company field, it is populated by customer->company field.
    When a particular company is selected, I would like the work_orders->person_calling field populated with the person calling for the selected company only. The user should be able to edit the person_calling field as well. Basically the person calling should be tied to the particular company. Ideally all persons calling should show up in the person_calling field in the appropriate record in the customer table as well. I hope someone can point me in the right direction.

    Right now this is how I have field rules set up:
    Field Type: User Entered

    Lookup styles: Table lookup
    Table: person_calling.dbf
    Linking Field: Company
    Display Order: Company

    Source: person_calling->Person_calling
    Fill: Person_Calling
    Display: Yes
    Width: 20

    Checked Items: Display as drop-down list box, User can add records to lookup table, User can edit records in lookup table.

    If I go over to the work_orders default browse, person_calling field is a dropdown, and I see all names entered regardless of which company is selected on the left. I can add an entry, and the default form appears, which lets me select the Company from the dropdown then type the name of the person calling. This in turn, appears in the person_calling table.

    I was told that I might need a lookup table for each company, for persons calling? That would be a lot. What is the best way to approach this problem. I apologize if this sounds confusing! I thought this would be easy, but I've been messing with this for about a week, day and night...getting burnt out! O.o

    Thank you in advance!

  • #2
    Re: Dynamically populate field choices.

    In defining the table lookup you are allowed to specify a filter immediately below where you fill in the display order. You need to filter the lookup based on the company field object value.

    I tested using a variable and that process works ok. If you are currently using table level field rules, and you can't edit those rules while the form is open, you will have an issue trying to refer to the form field object.

    You may need to remove the table level field rule lookup and change the Person_Calling object on the form to a List Box or a Record List - Edit Combo Box to achieve the same functionality.
    Last edited by Stan Mathews; 07-14-2011, 02:22 PM.
    There can be only one.


    • #3
      Re: Dynamically populate field choices.

      Stan, thanks for the reply. I have changed the Person_Calling object on the work orders form to a Record List - Edit Combo Box.

      I'm not experienced in creating filters, however. I tried to use the Filter Builder, where on the Condition1 tab, I set Company is equal to...."'
      The Value dialog box pops up. I imagine it's either the 'Specify a value now' or 'Specify a variable' radio button. I'm not sure exactly what to write in there. On my work orders form, the name of the company field is FIELD1. I'm guessing it's a little more complicated than just typing "=FIELD1" in the 'Specify a value now' option, since it tells me 'Company = FIELD1' is an invalid expression. Would you be able to help me with the syntax?

      Do I need to create a session variable?


      • #4
        Re: Dynamically populate field choices.

        The filter has to refer to the form field object by object name. You discover the object name by examining the properties of the object on the form. It is generally the same as the table field name but may differ.

        When referring to the form field object you then reference the object's value property to get the contents.

        So you might use a filter

        field1 = field1.value
        There can be only one.


        • #5
          Re: Dynamically populate field choices.

          Great, thanks Stan!