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

Filter table Lookup - field rules

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
    #31
    Re: Filter table Lookup - field rules

    G, You are correct. I am thinking why not apply both approaches?
    Is not all the times we need such condition. Some times will be beneficial to go progressive.
    There is no degradation of speed to have both options.
    Is it?

    Comment

      #32
      Re: Filter table Lookup - field rules

      Yes and very noticeable.
      If you do Progressive (or as some might want to call Cascading) lookup, you can use indices to narrow the range of searched records as you step from one field to the next. But if you do text search, you cannot apply an index here, alpha simply has to search the text of each field defeating the purpose of an index and markedly impeding the speed.

      Comment

        #33
        Re: Filter table Lookup - field rules

        Originally posted by G Gabriel View Post
        Theoretically speaking.. yes.
        Not a good idea though.
        You can search for a word across fields, very easily done BUT slow as Molasses as you will be searching every word in every field in every record.
        You don't see that in any search online. Most searches are structured and cascaded for a reason. Should be something to do as a last resort, not as a matter of routine.
        A search for a word across multiple fields can be made fast by using an index like the one defined in the product table - even with a lot of data

        Code:
        Index_Keywords_For_Category    KEYWORDSI(ALLTEXT(),VAR->EXCLUDED_WORDS)         Ascending    All
        The question is how to call that index from a fieldrule lookup..... It certainly can be done from an xdialog or in a typical find by key.
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment

          #34
          Re: Filter table Lookup - field rules

          So in the sample of post 24, we could not apply it?
          Or can we?

          Comment

            #35
            Re: Filter table Lookup - field rules

            Originally posted by Al Buchholz View Post
            A search for a word across multiple fields can be made fast by using an index like the one defined in the product table - even with a lot of data

            Code:
            Index_Keywords_For_Category    KEYWORDSI(ALLTEXT(),VAR->EXCLUDED_WORDS)         Ascending    All
            The question is how to call that index from a fieldrule lookup..... It certainly can be done from an xdialog or in a typical find by key.
            Yes Al, but how many indices you going to have? Are you going to have an index for each word you want to search? There is a delicate balance between using indices and how many to have. The fewer that serve the most purpose the better.

            Comment

              #36
              Re: Filter table Lookup - field rules

              Originally posted by JackForman View Post
              So in the sample of post 24, we could not apply it?
              Or can we?
              I didn't open Tim's zip file, just by reading his comments I am assuming that he did field rules lookup filtering out as you step from field to field using the previous field's value.
              In a scenario such as this you could use indices and would be very powerful. But if you use something that entails text search, you are in for a long ride.

              Comment

                #37
                Re: Filter table Lookup - field rules

                Originally posted by G Gabriel View Post
                I didn't open Tim's zip file, just by reading his comments I am assuming that he did field rules lookup filtering out as you step from field to field using the previous field's value.
                In a scenario such as this you could use indices and would be very powerful. But if you use something that entails text search, you are in for a long ride.
                Gab,

                you are right. the lookup works fine with few records... but when i tried to use it with almost 16 thousand records, my computer crawled and oftentimes hung when i tried to using 3 text criteria.

                has anyone found another way to accomplish this?

                regards to all
                Francis

                Comment

                  #38
                  Re: Filter table Lookup - field rules

                  Sorry for not getting back to this thread before now.

                  Originally posted by G Gabriel View Post
                  I didn't open Tim's zip file, just by reading his comments I am assuming that he did field rules lookup filtering out as you step from field to field using the previous field's value.
                  In a scenario such as this you could use indices and would be very powerful. But if you use something that entails text search, you are in for a long ride.
                  Gabe, your assumption was wrong but your prognosis was/is spot on.
                  This is the expression used in the field rule filter for the product field.
                  Code:
                  if(alltrim(vTerm)<>"",smatch(Category+Brand+Model+Description,"*"+alltrim(strtran(vTerm,",","*"))+"*"),.t.)
                  This is basically doing a text search within each record so definitely has a high overhead.
                  Originally posted by fddizon View Post
                  Gab,

                  you are right. the lookup works fine with few records... but when i tried to use it with almost 16 thousand records, my computer crawled and oftentimes hung when i tried to using 3 text criteria.

                  has anyone found another way to accomplish this?

                  regards to all
                  Francis,
                  I am attaching another sample. Different technique, using indexes. I made a UDF that grabs the list of keys from an index(including their record numbers). This list of keys is then filtered using the search term. Next a list of record numbers is created from the resulting list of keys. This list of numbers is passed into the filter in the lookup.

                  Will attach the sample shortly.

                  Edit: Hit submit by mistake so post not yet finished
                  Last edited by Tim Kiebert; 11-14-2009, 03:14 AM. Reason: Hit submit button by mistake.
                  Tim Kiebert
                  Eagle Creek Citrus
                  A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                  Comment

                    #39
                    Re: Filter table Lookup - field rules

                    tim, thanks. will wait for your sample
                    Francis

                    Comment

                    Previous 1 2 3 template Next
                    Working...
                    X