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

Help FR's conditional look up

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

    Help FR's conditional look up

    In a customer table I want to use the zip code look up table if the customer is in the USA.
    In the field rules for zipcode I used a condition;
    if country = "USA"
    This pops up Ok when country = USA but if the country is not the USA I get an error message when I enter the field. Is there a place for guidance on filling in the field rule sheet.
    I am inexperienced in A5
    Steve

    #2
    RE: Help FR's conditional look up

    Steve,

    Instead of the Conditional Table Lookup, I'd use a regular Table Lookup.

    Then, instead of pop-up on entrance I'd use pop-up conditionally on entrance. Pop-up the lookup table only when country = "USA".

    Then, I'd permit exceptions by specifying that 'Allow any value' is ok in the lookup field.

    -- tom

    Comment


      #3
      RE: Help FR's conditional look up

      Tom,

      Thanks for the thoughts but it doesn't seem to work.

      When I have a country other than USA, and I enter the postal code it looks up the code in the ZIP table. There are other countries besides the USA that use 5 digit zip codes

      Also, there is some secret that I forgotten such that when I do have USA and type in the zip code it goes to that zip. Currently, I have to use Find and then type in the number.

      Do I have to create a dummy table for countries other than the USA as it does seem that I need to use a conditonal look up.

      Thanks for your help
      Steve

      Comment


        #4
        RE: Help FR's conditional look up

        Steve,

        Just to be sure we are not looking at a trivial format issue the condition should be:

        country=USA (and I don't think you need quotes around USA unless you are in the expression builder)

        and not

        if country="USA" (as you wrote)

        I don't know if this is the source of your problem but it probably isn't helping anything.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Help FR's conditional look up

          Steve,

          Here's an easy example that illustrates what I had in mind. It addresses the issue you raised in the original post.

          Unzip the attachment to a separate folder. Do not mix it with your development work.

          Open the Names table using the default form.

          Enter a new record. If you enter USA in the country field, the zip code list pops up automatically. Otherwise, the lookup table does not appear and the user can enter the zip by hand.

          -- tom

          Comment


            #6
            RE: Help FR's conditional look up

            Tom,
            I don't seem to have made any progress. Your tables don't have CITY or STATE in. The purpose of the look up is to populate the City and State fields when a vendor or customer record is entered.

            When I add a CITY field to test your DB and enter in a ZIP code from a non USA country the USA city gets populated.

            The main purpose of wanting a conditional DB or condional look up is that I can use the information from the US ZIP code databases to populate US vendors or customers, but to have a free hand to enter NON USA entries.

            Bill, COUNTRY="USA" triggers the conditional pop up, but that is not the main problem

            Steve

            Comment


              #7
              RE: Help FR's conditional look up

              Steve,

              I did not know other countries had the same mailing zip codes as the USA.

              Adding city and state fields to my tables I see that entering a new record and a non USA country will lead to confusion if the user enters a zip that matches a record in the USA zip code list. The city and state fields get filled in.

              On the other hand, this isn't a problem if other countries don't use matching zips.

              I'll ponder the matter further.

              And, by the way, you're welcome.


              -- tom

              Comment


                #8
                RE: Help FR's conditional look up

                Steve,

                Maybe this example will be more realistic.

                Unzip it to a separate folder. Do not mix it with your development work.

                I've added City and State fields, and I've added Conditions to the 'field fill in' specifications. The "Condition" column in the field mapping table can be used to specify that a field is only included in the lookup in some cases. If the expression you write evaluates to True for a record, the value is coopied to the current record. Otherwise, the field is not filled.

                -- tom

                Comment

                Working...
                X