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

Error 20 when Creating FullText Index

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

  • Error 20 when Creating FullText Index

    I'm getting the Error 20 messagebox while creating a fulltext index on a memo field on a large table.

    Where do I find the error reference info for error numbers and names?

  • #2
    Re: Error 20 when Creating FullText Index

    can you give us an idea of the exact way you tried this. I had never thought of indexing a memo field, but someone probably has tried to or did it if it is possible.



    .
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


    • #3
      Re: Error 20 when Creating FullText Index

      Originally posted by stanlyn View Post
      I'm getting the Error 20 messagebox while creating a fulltext index on a memo field on a large table.

      Where do I find the error reference info for error numbers and names?
      Error Functions

      But I don't get a translation for error code 20.

      I just created a full text index on a memo field in a test table I have. Didn't get an error.

      Are you using define index and pressing the Full Text Search button or trying to build it your self? I used the button..
      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


      • #4
        Re: Error 20 when Creating FullText Index

        I used the define index and pressing the Full Text Search button then selecting the memo field.

        This is a production table that has about 650,000 records and each memo field contains about 2500 characters. It runs about 2-3 minutes before issuing the error.

        The table is good as I can filter the same memo field for some words and it completes without error. I am assuming that each record's memo field is scanned.

        How can I find the record number at the point the error 20 is generated, so I can look at that record?

        Comment


        • #5
          Re: Error 20 when Creating FullText Index

          But I don't get a translation for error code 20.
          Isn't there a error number and name reference in the help files so one could review them by either name or number? I saw some sort of code that speaks of translating, and if that is all that alpha has on its error codes, then I consider it weak in communicating error issues.

          How can I trap errors and gracefully recover from them? I need this as many time I can anticipate certain errors and I need to check for them in advance and then programitically do something about them...

          Comment


          • #6
            Re: Error 20 when Creating FullText Index

            My previous post was supposed to link to the error functions in the help file.

            To find a record that is causing your index error, you'll need to divide the table until you find the error. Use the copy operation and cut the file in half and see which half the error occurs in. Then keep dividing that part in half again until you get the record with the error.
            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


            • #7
              Re: Error 20 when Creating FullText Index

              To find a record that is causing your index error, you'll need to divide the table until you find the error. Use the copy operation and cut the file in half and see which half the error occurs in. Then keep dividing that part in half again until you get the record with the error.
              You got to be kidding.......

              There is nothing wrong with the table as I have also verified if with fox by building a full text index on it...

              Isn't Alpha's full text indexing routine built with xbasix or A5 functions and calls so that a piece of code could be inserted into it that would allow output to a file, or echoed to the screen?

              Anyone care to write some code that would start ate the beginning of the table and traverse the table until the end while writing/appending the contents of the memo field to a log file with its record number. I'd do it myself, but it would take a long time to figure out this seamingly trival task... If the full text indexer worked as expected, we wouldn't be talking about this here.

              Thanks...

              Comment


              • #8
                Re: Error 20 when Creating FullText Index

                My previous post was supposed to link to the error functions in the help file.
                Thanks for that, however where is the list of possible errors and their associated remedies published.

                Comment


                • #9
                  Re: Error 20 when Creating FullText Index

                  I tried building the full text index again in A5 and after 29% I get a different error...

                  "Can't add tag to compound index"

                  It did run longer this time...

                  Any ideas?

                  Comment

                  Working...
                  X