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



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
  • Time
  • Show
Clear All
new posts

  • <table>.fetch_find()

    I read in the documentation regarding <table>.fetchfind() as follows:

    If <TBL>.FETCH_FIND() is successful, the found record is retrieved and its Record_Number is returned. If no exact match is found, a negative number corresponding to the record number of the closest matching record is returned.

    However, for example, I have found that a search "abcd" will report a +ve record number pointing to record "abc" where no "abcd" exists as the field and index is only 3 characters long. I would have expected a negative number for "abcd" as it is not an exact match. Obviously the extraneous characters are ignored.

    Version is 4130_3033.
    Last edited by Garry Flanigan; 12-01-2006, 03:31 AM. Reason: realised problem - search string longer than index

  • #2
    Re: &lt;table&gt;.fetch_find()

    Originally posted by Garry Flanigan View Post
    .... I have found that a search for say "abc" and "abcd" will find the same record where the value is actually "abc" and no "abcd" exists. I would have expected a negative number for "abcd" as it is not an exact match. This seems like a bug to me or have I missed something?

    Version is 4130_3033.

    PS. Fortunately, the lookup function does only find the correct exact match, so I will use this instead.
    I do not think this is a bug. It is just that in the context where <TBL>.FETCH_FIND() is typically used, "abcd" is an "exact match" for "abc" as the former "exactly" (!!!) contains the latter. Maybe the wording in the documentation is a bit misleading but this is the way <TBL>.FETCH_FIND() should work. As you noted, there are other methods to do other things in other contexts.



    • #3
      Re: &lt;table&gt;.fetch_find()


      You were very quick with a reply!!

      Note that I did some more research and altered my original post. It relates to extraneous characters being ignored. However, I would not call such a match an exact match and consider the documentation to be misleading.


      • #4
        Re: &lt;table&gt;.fetch_find()

        Garry, I don't recall bumping into this situation before and can see why the result surprised you. Suggest you submit a bug report and use it to suggest specific change to the documentation.


        • #5
          Re: &lt;table&gt;.fetch_find()

          The documentation may be slightly misleading, but it is correct.

          "Alpha Five will automatically pad the Matching_Expression with trailing blanks if necessary so that the length of Matching_Expression matches the index key length." (bold added for emphasis).

          While it isn't normal to enter an expression that is longer than the field length, the help text indicates that the expression length will be altered to match the field length. Therefore, if the field is only 3 characters, and there is a record with a value of "abc" , searching for "abcd" will have a match, as the expression "abcd" will be truncated to match the field length of 3.

          If it is expected that some search expressions may be longer that the field length, there are a couple options. The best is to limit the expression length to the field length. Since the use of fetch_find() indicates it is being used in a script, it would be easy to check the length of any entered expression using len() and output a message to the user to tell them the expression entered is too long.

          The second is to make the field longer, even if only 3 (in this example) characters are used. The fetch will add blanks to the actual field lenght.


          • #6
            Re: &lt;table&gt;.fetch_find()

            Jerry, good morning.

            I agree the documentation is correct, but it's correct only as far as it goes. While addressing the behavior of the method if the Matching_Expression is shorter than the index key length, it does not address the behavior of the method if the Matching_Expression is longer than the index key length. Since subtleties are lost on me (according to my wife), an explicit description of the behavior would improve the documentation... at least for me.