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 DB Lookup Filter

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

    Conditional DB Lookup Filter

    I want to set up an order entry system for sales reps of multiple manufacturers. On the order entry header (OrdHedr BD), I select a manufacturer for that order. When I get to the order detail section (OrdDetl DB), I want to be able to ONLY enter the items from that manufacturer.

    I have the MfgID number in each item record in the Items DB and I have tried a Conditional DB lookup using the Items DB with the filter as follows: TRIM(OrdHedr->MfgID)=TRIM(LOOKUP->MfgID) Item DB lookup is linked via an index on the item number. To ensure that I can only enter items for that manufacturer, I have the field rule validation set to "Exists".....

    This ALMOST works!!! The resulting lookup does, in fact, have only the items for the manufacturer selected, I can directly enter items for that manufacturer, I get an error message from validation if I enter an item that isn't in the DB - but I CAN enter OTHER manufacturer item numbers without getting an error message from validation ALSO!!!

    Should not the Conditional DB filter limit not only the selctions shown in the lookup but also limit the items to those same selections if the validation field rule is set to "Exisits"??? It isn't for me!! Any help I can get will be appreciated!!!

    Thanx all.....

    #2
    RE: Conditional DB Lookup Filter

    Hi Dean

    Have you looked at Validate trigger in Field rules?


    Try creating a script called "TrigCheck"

    that gets @sys_field_value and uses that value with "Xlookup" to see if that value is valid. You will probably need an index using the manufacturer and item fields.

    I have done something similar and doesn't allow an invalid value.

    Hope this helps

    Robert

    Comment


      #3
      RE: Conditional DB Lookup Filter

      Robert,

      Thanx for your reply. We are now pushing the limits of what I have learned with A4... Scripts are, by far, the weakest part of my A4 knowledge.... Thus, could you be a little more specific in what I might want in this script. I understand that you want me to use the script in the vaidate trigger and understand what that can do, but when using system varuables, I start to get lost if I didn't "make" the variable myself !!!! Just a little more of a push and I hope I can get it.... Thanx....

      Comment


        #4
        RE: Conditional DB Lookup Filter

        I didn't mention that I included zipped files that will demonstrate what happens.... Unzip and open ordhedr set and enter an order... Use "MR" as a manufacturer when prompted for such... Then, see the "MR" items in the lookup table in the region. See that you get an error if you enter an eroneous number (ei "zxcvb")... but, notice that you can enter "PEG 32" as a stock number (item nuumber) when "MR" is selected as Mfg, but "PEG 32" is an "SF" item number!!!!! "PEG 32" is NOT a table item (is not included in filtered search), but can be netered "directly" without an error message from validate field rule!!!! Hope this helps....

        Comment


          #5
          RE: Conditional DB Lookup Filter

          Hi Dean

          We have a problem, I use A4V4 so I cannot access your set or your forms.

          There are two fields which determine the values in my conditional lookup for the Contact.Dbf

          ..Int_make = Ford
          ..Vehic_type = Car

          These two field then select out Ford Cars for my lookup.

          ..Vehic_desc = Taurus

          My lookup table has three fields

          lookup->Vehic_make
          lookup->Vehic_type
          lookup->Vehic_desc

          The script "Read_mak" is put in the field rules enter trigger for "Vehic_desc" in Contact.dbf

          ..Read_mak->{set�%interested_make,�ltrim(rtrim(teletrac->int_make))}

          %interested_make gets the Manufacturer.

          The filter makes sure that the lookup selects only vehicle descriptsion for Ford Cars
          This is my Conditional db which is set to exists and will not allow me to save a record unless it finds a match.

          Expression : trim(INT_MAKE)=LTRIM(RTRIM(%INTERESTED_MAKE))__________________
          Database : C:AUTOMAKRCAR_MAIN.DBF
          Link index : CAR_DESC
          Display index : CAR_DESC
          Filter : trim(LOOKUP->VEHIC_type)=trim(VEHIC_TYPE).AND.TRIM(LOOKUP->VEHIC_MAKE)=TRIM(INT_MAKE)_

          --------------------------------------------------------------------------------
          Otherwise use:
          Database : C:AUTOMAKRCAR_MAIN.DBF
          Link index : CAR_DESC
          Display index : CAR_DESC
          Filter : trim(LOOKUP->VEHIC_TYPE)=trim(VEHIC_TYPE)


          Page three in the field rules is as follows:

          TELETRAC->INT_DESCRP

          Lookup : Yes No
          Lookup Source : Advanced
          Advanced Option : conditional Db
          Lookup Validation : Exists
          Allow Exceptions : Yes
          Location : 5
          Rows in Window [1-15] : 15
          Auto Popup : Yes


          Hope this helps

          Robert

          Comment

          Working...
          X