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

Lookup On Conditional Field

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

  • Lookup On Conditional Field

    I have a lookup set up on a conditional field and I need to make it to where the lookup will not pull in anything if it does not match exactly. Right now if you pull in the information from the lookup it will change the calculated field and the fields that it is calculated from.


    I had to build this lookup on the form level to get to work. I am having issues with employees pulling in the wrong information when what they enter is not in the lookup table.

    Can anyone help me figure out how to get Alpha Anywhere to not let information be pulled in unless the fields match?

    Hope I explained this correctly

    thanks

  • #2
    Re: Lookup On Conditional Field

    The standard table lookup by default does not allow user enterd values (unless you set options on).

    Comment


    • #3
      Re: Lookup On Conditional Field

      Even the default setting allows you to pull the incorrect information in,

      Originally posted by Ray in Capetown View Post
      The standard table lookup by default does not allow user enterd values (unless you set options on).

      Comment


      • #4
        Re: Lookup On Conditional Field

        What does "pull in" mean?
        Does that indicate that it is not a user keyed entry but one that was pulled out of the look-up table?
        Any way, check settings is all I can suggest without a sample.

        Comment


        • #5
          Re: Lookup On Conditional Field

          i have tried all the settings.... I cant figure it out. And yes the information is brought in from the lookup table if the look up field matches, but I cant figure out how to make it not come in if it doesnt match.

          Comment


          • #6
            Re: Lookup On Conditional Field

            Alli,

            It's not clear to me what a "conditional field" might be? Is this a field in your table? Have you tried to define a table lookup field rule for it? Are you saying the rule is set to "force closest match", but the users are picking the wrong values on purpose or by accident?

            Comment


            • #7
              Re: Lookup On Conditional Field

              I meant a calculated field. I had to define the lookup on the form level. I have tried all the settings and no matter what they can pull in the wrong info. They are doing it by accident but it needs to be invalid unless they match perfectly. Its for data entry

              Originally posted by Tom Cone Jr View Post
              Alli,

              It's not clear to me what a "conditional field" might be? Is this a field in your table? Have you tried to define a table lookup field rule for it? Are you saying the rule is set to "force closest match", but the users are picking the wrong values on purpose or by accident?

              Comment


              • #8
                Re: Lookup On Conditional Field

                Not making much sense - it is brought in if it matches, what comes in then if there is no match - probably the closest match.
                If there is no match then you want the user to clear the field ? why have a lookup for no match?
                Sample
                sample sample
                otherwise this gets silly.

                Comment


                • #9
                  Re: Lookup On Conditional Field

                  Alli,

                  I asked 4 questions and you responded to one of them. Not a passing grade. Not helpful to effective communication.

                  Let me add other questions. Please take your time and respond to all of them. If the questions themselves are confusing to you let us know that, also.

                  5) the "calculated field" ... is it a calculated display field that exists in your form only, or is it a table field for which you have defined an expression to compute a result?

                  6) concerning the "calculated field" ... what's the expression you've used to define the computed result you want?

                  7) what does "match perfectly" mean?

                  8) when they pick a value off the lookup list how might Alpha Five "know" that there's a mismatch?

                  Comment


                  • #10
                    Re: Lookup On Conditional Field

                    Hey Tom, this is Alli's manager Jim, I'll try and give you a precise answer.

                    I asked 4 questions and you responded to one of them. Not a passing grade. Not helpful to effective communication.

                    Let me add other questions. Please take your time and respond to all of them. If the questions themselves are confusing to you let us know that, also.

                    5) the "calculated field" ... is it a calculated display field that exists in your form only, or is it a table field for which you have defined an expression to compute a result?
                    Form only

                    6) concerning the "calculated field" ... what's the expression you've used to define the computed result you want?
                    RIGHT('0000'+ALLTRIM(STR(BOOKMAP)),4)+RIGHT('00'+ALLTRIM(STR(PAGE)),2)+ALLTRIM(LOT)

                    7) what does "match perfectly" mean?
                    Alli means a exact match into the lookup table. If there is no exact match the dropdown menu will still "point" to a record in the lookup table. Herein lies the problem, Employees are selecting records that don't match and introducing errant data

                    This is a match
                    match.JPG

                    This is not a match
                    lookup.JPG


                    8) when they pick a value off the lookup list how might Alpha Five "know" that there's a mismatch?

                    Alpha Five "knows" because it will place a check mark by the corresponding record shown in the drop down list. This is what we're trying to find out. The drop down list is a range of records near the key you are searching for. If the search key matches the key in the lookup table a check mark is displayed. Since the code that does the matching and pulls the range of records is behind the scenes, we're not sure how to tell if Alpha Five "knows". If this were a webpage it would not be a problem. The SQL result set would be null and nothing would be displayed in the drop down list.

                    thank you,

                    Jim Patterson
                    General Manager
                    The Information Market.

                    Comment


                    • #11
                      Re: Lookup On Conditional Field

                      Jim, thanks.

                      Let me try to restate the issue. Tell me if I'm getting closer to understanding.

                      You have a calculated display field on your form that computes a value. i.e. map, page and lot to uniquely identify a property

                      You want to "lookup" additional information about that property from a separate table, and have chosen to use a table lookup field rule so the user can search for the property using the computed value in your calc display field. The users are selecting the wrong properties and Alpha is not alerting them that the value they've chosen is different from the calc display field value.

                      If this were me, I'd abandon the use of a table lookup that relies on the user being careful enough to select the correct property. Instead, I'd retrieve the additional data using one or more of the lookup() functions. Lookup(), LookupC(), LookupN(), etc. These will return field values from the "Lookup" table only if there's a match. These could be incorporated into the rules for the form, or a script could be written to collect the desired field values all at once, running from a button push or some other appropriate event in your design.

                      An alternative would be to include validation routines in your present approach. These would run before the record is committed to disk, and would block the save if there's a mismatch. The script that does this could remove the offending field values for you.

                      Later...

                      I suppose yet another approach would filter the lookup list to show only matching values.
                      Last edited by Tom Cone Jr; 02-18-2014, 12:08 PM.

                      Comment


                      • #12
                        Re: Lookup On Conditional Field

                        The way that I did this: I chose the look-up to be an edit combo from the same table the search was happening - that way a user can only enter a value that is in there to start with. You can filter that same look up - this allows for department, user, or about anything if you use a variable to filter on.
                        If the user selects the number they are looking for then only that record will show.
                        Hope that helps.
                        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                        Comment


                        • #13
                          Re: Lookup On Conditional Field

                          Hi, Charles.

                          thanks for your post.

                          It's more than a little disappointing that the original poster has seemingly wandered away...

                          Comment


                          • #14
                            Re: Lookup On Conditional Field

                            It happens, life can be a rat race at times - no worries. Perhaps he figured it out, no longer needs advice or just changed strategies. Either way, I figure someone else may have that moment of clarity we have all felt when you suddenly realize what you need to do from one of the posts made!
                            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

                            Comment

                            Working...
                            X