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

conditional lookup table quetion

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

    conditional lookup table quetion

    hello:

    does anyone know if it's possible to base a lookup on a field in the current record that's being entered?

    i'll try to explain.
    lookup table has this data like this (i'll post the actual dropdown, too):
    cubill cuship cuname
    1234 1234 name
    1234 1234A name
    1234 1234B name
    5678 5678 name
    6789 6789 name
    when I enter 1234 into the bill to field on the formform, I only want to see the cuship values that begin with 1234. no matter what I try, I can't get this to happen. I always see the entire list. when I put a formula in the filter field rule condition, the filter is applied to the entire table. so, if I use cubill $ cuship, I get all of the records with no letter after the first 4 numbers. it's filtering the entire table
    I want to filter the ship to list based on the bill to that was entered.

    here's what I get:
    a1 Capture.PNG
    here's what I want to achieve. I did this by hard coding 2025 into the filter field.
    a2 Capture.PNG

    thanks and I hope I explained it well enough. i'm tempted just to write my own xdialog. probably could have for as long as I've messed with this.

    #2
    Re: conditionla lookup table quetion

    I've kinda gotten around it by entering a field event on the bill_to field onwrote event. I just make the ship_to = to the bill_to and the dropdown goes to that entry. then all of the locations with the letter designation are listed right below. at least the user won't have to scroll the entire list or use as find.

    Comment


      #3
      Re: conditionla lookup table quetion

      I was going to suggest that you simply need a better filter. If this were a multi-tenant app or if you were to reuse these numbers with another customer you might get the wrong info popping up. This is very similar to another post I saw last night. A four digit number can only have so many combinations, if your filtering a drop down based on a four digit number using a progressive match - you will get 24 returns once all combinations exist, this of course is assuming your not re-using digits. A 5 digit column will return 120 variations - so a progressive or contains match might not be a good idea in the first place which is why you were getting so many returns.

      I would suggest a much more unique filter for the drop-down and also include or exclude the possibility of a null value - trust me users find a way to present a problem, lol. Try to look at your data to define what makes that particular record absolutely unique.
      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


        #4
        Re: conditionla lookup table quetion

        I don't think you can filter a table lookup as you want. My attachment uses a filtered record list - list box defined for the form.

        cuinv.zip

        The same or similar can be done with form level field rules.
        Last edited by Stan Mathews; 07-14-2017, 11:22 AM.
        There can be only one.

        Comment


          #5
          Re: conditionla lookup table quetion

          thanks charles

          Comment


            #6
            Re: conditionla lookup table quetion

            thanks for the example stan. i'll give it a try. my follow-up may be good enough, though.

            Comment

            Working...
            X