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

Can this routine be made quicker!

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

    #16
    Re: Can this routine be made quicker!

    Thanks Tom,

    I think I have quite a few options to try (especially after further investigation of the users requirements), the main problem is that the app used a one size fits all aproach to matching when something a little more inteligent would actually be much more effective.

    I believe I can use the index lookup method on simple zip/postal code searches, and the more intensive multi string lookup loop for the multi field matches.

    Your example routine can definatly be used Tom, especially as I have now found that there appears to be many circumstances when a single partial zip search is sufficient.
    Chris Tanti
    Technical Support

    Nuance & Fathom Ltd - The data-driven marketing agency

    Comment


      #17
      Re: Can this routine be made quicker!

      Chris:
      Are these data growing:? If so, which table?

      Comment


        #18
        Re: Can this routine be made quicker!

        No it doesnt grow, they purchase sample and load it into the process table, based on the requirments of a particular job. Each job will have a custom match file as well.
        Chris Tanti
        Technical Support

        Nuance & Fathom Ltd - The data-driven marketing agency

        Comment


          #19
          Re: Can this routine be made quicker!

          Chris:
          You have two tables:

          Table: Match
          Field: match1
          Field: match2

          Table: Process File
          Field: Address

          The problem you are running into, is trying to test match1 & match2 against Address to see if address contains any matching values.

          Address is a concatenated field that contains, among others, values that correspond to either match1 and/or match2

          I think you see were I am going with this:
          Extract these values from Address into separate fields that would be identical to match1 & match2.

          I would create two fields in Process File Table, same as match1 & match2.
          Run an update operation on Process file table to extract those values from Address into these fields.
          Now you have two tables with identical fields and it seems to me that, once a match is found, you are taking values from Process file table to update values in match table.
          I would simply run a "post" operation, using match as master, Process file as transaction.
          To summarize:
          1-Create two fields in Address & run an update operation. Since the data in this table is static, you will do this once.
          2-Run a post operation.

          Comment


            #20
            Re: Can this routine be made quicker!

            Thanks for the sugestion, it should be noted that the match is based on partial strings not whole words, so posting isnt going to be appropriate.
            Chris Tanti
            Technical Support

            Nuance & Fathom Ltd - The data-driven marketing agency

            Comment


              #21
              Re: Can this routine be made quicker!

              posting isnt going to be appropriate.
              For matching fields: use *ANY()

              Comment

              Working...
              X