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

Another way to find a record, besides tbl.fetch_find?

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

    Another way to find a record, besides tbl.fetch_find?

    Good day,

    Question:
    I know that I can use tbl.fetch_find in a xbasic UDF to find a record when I know the value of a field(s), but I was wondering if there is another way to find a record.

    Background:
    I want to test if a record exist that contains tbl.firstname = �firstname� and tbl.lastname = �lastname�. And currently I�m using rec = tbl.fetch_find(firtname +lastname) but that does not correctly check for the existence of this combination.

    Kind regards
    George

    #2
    Re: Another way to find a record, besides tbl.fetch_find?

    George, I'd use the key_exist() function after first defining an indextag based on the concatenated string values of the two fields. i.e. firstname + lastname. If the concatenated string value already exists in the list of keys in the index the function will return "True", and you'll know that a record with those field values is present. Otherwise it returns "False".

    -- tom

    ps. your existing approach will also work but again you need to define a compound key and then pass a search term that matches the indextag expression. If you're having trouble it's because either the index is not defined correctly, or you're passing an argument to the function that doesn't match the indextag expression. Trailing blank spaces in table fields can often cause mismatches that are not obvious. In any case, I don't favor doing it this way however because you're opening new instances of both the table and the index. Key_Exist() just opens the index.

    Comment


      #3
      Re: Another way to find a record, besides tbl.fetch_find?

      A5_GET_RECORDS_IN_QUERY() is very flexible and easy to use for checking for the existence of records that match an expression.
      Jim Coltz
      Alpha Custom Database Solutions, LLC
      A5CustomSolutions.com
      [email protected]

      Comment


        #4
        Re: Another way to find a record, besides tbl.fetch_find?

        And possibly another way is to use lookup() which takes a filter and your table doesn't have to be opened.
        http://support.alphasoftware.com/alp...s/LOOKUP().htm

        or even lookupc() if you have an index name to use so is very similar to Tom's approach.

        These actually return a field's value but all depends on what you need.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Another way to find a record, besides tbl.fetch_find?

          Hmm, my initial post was not that clear. So I need to add that after determining wheter first & lastname exist in the table, I need to get something back that will allow me to update the record IF it exists.

          Looking forward to your response.

          Regards
          George

          Comment


            #6
            Re: Another way to find a record, besides tbl.fetch_find?

            George, if your design is using the combination of firstname + lastname to find records then I'd recommend you create a new index and use an expression to define the index key as the string of characters you get when you concatenate the two fields. You should give some thought to how you're going to arrange for the user to tell you which first and last names to search for. The input strings they supply will have to be massaged to match the structure of the expression you use in the index you define. Remember to take the trailing blanks into consideration. The new index can then be used with the fetch_find() method of the table. If this isn't making sense to you let us know. We can cobble together an example for you, just tell us how you're going to get the names from the user. Even better supply us with a working copy of your form with supporting tables.

            Comment


              #7
              Re: Another way to find a record, besides tbl.fetch_find?

              Good point Tom,

              I was trying the "index" method etc, but because I was not getting it to work, I started looking for alternatives. I will gather my facts and post it here, for asistence from people like yourself.

              Kind regards
              George

              Comment

              Working...
              X