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

Howto - Lookups � Previous values

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

    Howto - Lookups � Previous values

    Suppose I have the following table:

    Field1 Field2
    #1 A 100
    #2 A 200
    #3 B 100
    #4 B 300

    I want to use a drop-down list box with previous values on field2, but only with matching field1 values. So when record #1 is selected (Field1 is A), I want to get 100 and 200, not 300 (Field1 is B).

    When I define a lookup-previous values rule for Field2, I always get all values (100,200,300).
    Adding a filter to the rule like:
    Field1 == var-"curr_field1 (where curr_field1 is set to the value of field1 I want to see)
    doesn�t work neither. Because Field2 with value 100 is only indexed once (unique values), I get this value only if curr_field1 is A, not with B.

    Is there a way to work around this without the use of a separate table?

    Setting a lookup-previous values rules creates an index with unique value of the field. Tried to change this index by hand, but A5 isn�t tricked by this and simply creates a new one.

    Wouldn�t it be more flexible to have something like an �Index Lookup� as one of the lookup styles with the same functionality as �Previous values�, but where the index isn�t determined/built by A5 and you have to select one of the existing indexes of the table?

    BTW noticed:
    When setting a filter for a lookup style, the option to select variables in the Expression Builder isn�t shown, but F6 works.
    Tags: None
    #2
    RE: Howto - Lookups � Previous values

    In the field rules, lookup tab, there is an option to enter a filter, so

    FIELD1 = CURRENT(FIELD1)

    should work :)

    Comment

      #3
      RE: Howto - Lookups � Previous values

      field1 = current(field1)
      This filter didn't work either with my table, all previous values showed up in the popup without consideration of field1.

      Didn't expect it to work anyway, still only 1 of the records with field2=100 is indexed, so it would only show up with field1=A or field1=B, not both.

      For further testing I created a table exactly as in my example with just field1 (1 character) and field2 (3 digits) and set the filter on field2 accordingly.
      First of all, A5 didn't create an index when the filter was set. I entered the four records and after that a popup on field2 didn't show anything at all.
      Also saving the default form, left me with a grayed-out form in the Control Panel. It couldn't be opened, nor changed, just deleted.

      Comment

        #4
        RE: Howto - Lookups � Previous values

        Please forget the previous about A5 not building an index when a lookup-filter was set on field2. My mistake, field2 was numeric, changing it to alphabetic solved it. (not the lookup previous values itself).

        Comment

          #5
          RE: Howto - Lookups � Previous values

          Jos,

          Please, tell us how you did it.
          What is the esxact fieldrule for the lookup?

          Ton
          Most things are simple but unfortunately only after the first time

          Comment

            #6
            RE: Howto - Lookups � Previous values

            Ton,

            Sorry, don't understand the questions, to what do you exactly refer?

            Jos

            Comment

              #7
              RE: Howto - Lookups � Previous values

              Jos,

              You worked on a fieldrule for the lookup with a filter,
              but field1=current(field1) was not working.
              Can you give me an example of how you finally fixed it?

              prettig weekend

              Ton
              Most things are simple but unfortunately only after the first time

              Comment

                #8
                RE: Howto - Lookups � Previous values

                Ton,

                There is no way to fix my problem with the current lookup field rules. At least I didn't come up with a solution, nor did I get a reply that helped.

                The problem itself doesn't exist anymore, I decided to use seperate tables in designated directories. But that goes beyond the scope of this discussion.

                ook een prettig weekend gewenst,

                Jos

                Comment

                Previous template Next
                Working...
                X