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

corrupted indexes

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

    corrupted indexes

    I have accidentally found a way in Xbasic to consistantly generate the following error message (with its' spelling error):
    ""**ERROR:Itis possible that your indexes have become corruptec. Try to update indexes by right-clicking on the table in the Control Panel and choose the Update Indexes command. -" line 322, script "GMUnified""
    The GMUnified script line it points to is a "table.enter_end(.T.)" command. The Alpha5V5 has the latest update. This is a relatively small database, with only about 40K entries in the target table, and this should not be happening. How do I stop this?
    I have zipped up the entire database (about 6-1/2 meg) along with a document on how to duplicate the problem and placed it on my FTP site if you want it. Email me for the FTP user and log-in.

    Rick Smith

    #2
    RE: corrupted indexes

    "table.enter_end(.T.)"

    likely this should be

    "tbl.enter_end(.T.)" or something similar based on whatever pointer is created with your

    pointername = table.open("tablename")
    or
    pointername = table.current()
    There can be only one.

    Comment


      #3
      RE: corrupted indexes

      It is a table pointer. The actual pointer name is custbl (ftom custbl=table.open("cus.dbf") and the statement is custbl.enter_end(.T.)

      Comment


        #4
        RE: corrupted indexes

        Have you tried the usual database compact to see if that helps?
        There can be only one.

        Comment


          #5
          RE: corrupted indexes

          Yes. It has no effect on the problem.

          Comment


            #6
            RE: corrupted indexes

            Do you set an index in the script? Is that index in force during the record enter? Remove the index
            Finian

            Comment


              #7
              RE: corrupted indexes


              Oops, I should be in bed. Last week I had to deal with a very similar situation in V4.5. A record save of a new record was generating the same error.

              Before you go through my suggestion below make sure that you first go to the indes builder for the problem table, highlight the indexes, Ctrl-X to remove them then click the "Build Indexes" lightning bolt. This will remove the index file. Then Ctrl-V your index definitions back in and rebuild. This is the only way to ensure that you don't have a "benign" index corruption (which would be fixed by following these steps). Now enter some records in your table like before. If the problem recurs, try the next suggestion.

              My only solution for my problem was to remove the index on one field since the problem only occurred when a value of "D7140" was added in that field to this particular table at one customer. Fortunately this was a benefit for me, since the index was no longer required. Even more fortunately it wasn't a key index.

              Check the indexed fields in the table one by one, entering records in which you add a value to only one indexed field at a time. If adding a value in one field causes the enter to fail then you have a suspect. If removing that index causes the problem to go away, then maybe the folks at Alpha might look at the table.

              I still have my problem table so I'm going to check it again tomorrow to see if I can verify/duplicate the results.

              Finian
              Finian

              Comment


                #8
                RE: corrupted indexes

                Tried all suggestions. No change. Same error. I can't get rid of it. The table only has about 40K records. I even tried updating the production indexes every 100 new records, closing then re-opening the table. Nothing I do changes the error. I've been writing Xbasic for over two years and have never seen anything like this. I think I need some Alpha Five help on this one.

                Rick Smith

                Comment


                  #9
                  RE: corrupted indexes

                  How many indexes do you have on the table? Can you drop them all and still do test entry?

                  F.
                  Finian

                  Comment


                    #10
                    RE: corrupted indexes

                    There are only two indexes. I'll try killing all indexes and see what happens.

                    Comment


                      #11
                      RE: corrupted indexes

                      I forgot that the software checks the indexes because it needs them to make sure there are no duplicate customers. I deleted both indexes and it restored them, ran a little, then gave the same error message as always. The software will not run without the indesed. The indexes are for the customer's last name (char, 30), and customer ID (numeric, 12.0) .

                      Comment


                        #12
                        RE: corrupted indexes

                        Unfortunately testing like this is tedious and almost always involves tearing apart what you ahve spent so much time putting together.

                        Most likely, one of them is causing the problem and you can't fix things until you find out which one. How long does it take for the error message to show up? In mine it only took entering 3 or 4 records at the most. You need to make enough changes so that you can do some test entry without one index. If the problem is what I think, it will appear everywhere including the default form.

                        F.
                        Finian

                        Comment


                          #13
                          RE: corrupted indexes

                          Richard, What version of Windows are you using & are you on a network?

                          Comment


                            #14
                            RE: corrupted indexes

                            I'm running XP-Pro with SP1. I'm running stand-alone with a cable modem access to the web, and the software processes over 700 records before it gags. I have manually reviewed the records and have found nothing unusual. Unfortunately, this one isn't simple.

                            Comment


                              #15
                              RE: corrupted indexes

                              Is this happening in an update or other batch process?

                              If that's the case are you using or can you use batch_begin/batch_end?

                              F.
                              Finian

                              Comment

                              Working...
                              X