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

Lost Indexes: Return of the Thread

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

    Lost Indexes: Return of the Thread

    Howdy All.

    I did a search on this topic, and it seems to have reared it's ugly head almost as many times as Sauron in Lord of the Rings.

    Anyhoo...

    I had an entire set of indexes for a table simply vanish on me yesterday. When I switched into form mode on my main employee data entry table, I got an error saying the index or query could not be found. I had been doing a "Set Index" script on Form.Activate...set the index to something very simple...index on "EmployeeID" Ascending order. When I got the error message, I ran a pack, then I ran a "rebuild indexes" script. Still got the error. When I looked at the indexes for the table I found they were all gone. Nada. Zilch.

    I have backups, but I'm very curious to know if anyone else has had this problem, and if so, what did you do to fix it? This is a cause for concern for me as this DB is not even in production yet. Just me using it and I'm concerned about stability.

    Thanks for any info.

    Dennis Jones

    #2
    RE: Lost Indexes: Return of the Thread

    Dennis,

    Are you running any A5 add-ons? I ask because I'm also relatively new to Alpha 5 (about 4 solid months now) and have experienced this issue once so far about 6 weeks ago. Of course that makes it hard to pinpoint, but my intuition points me in the direction of an add-on. (My 2nd choice would be Alpha5 freezing up and requiring a Task Manager shutdown or full system re-boot, but that should just corrupt an index, not remove it entirely.)

    I'm quite familiar with the Sequiter CodeBase product Alpha 5 uses for working with FoxPro tables. It has some bugs related to memo fields (mostly not recovering nicely when there's a failure in that area), but otherwise it's rock-solid. However, since everyone who uses CodeBase "rolls their own" c4dll.dll from the source code, it's possible that some hidden bug crept in there during that process. Anyway, just my 2 cents.

    --Michael

    Comment


      #3
      RE: Lost Indexes: Return of the Thread

      Michael:

      Thanks for the reply.

      We did download the A5Doc add-on a couple of days ago for eval purposes. I hope that didn't cause the problem. Would hate to think this happens whenever an add-on gets thrown in.

      Comment


        #4
        RE: Lost Indexes: Return of the Thread

        No, A5doc wasn't the problem. I've never heard of anyone having a satisfactory explanation as to what causes it, but a remedy I have in place for clients is I copy *.cdx to a folder within the db's folder - and when they get an error "tag name not found" they can go to my Utilities and press restore indexes, which copies all the indexes from the 2nd folder to the db's folder, and then rebuilds all indexes.

        If you do this, then you need to be sure the form that the button is on is based on a dummy table, that has no indexes - usually the same table you base your master menu on. Also, you will have to refresh the backup cdx's as you continue in development.
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          RE: Lost Indexes: Return of the Thread

          Another method; not necessarily better - just different....

          I have a function that actually writes a script to completely rebuild the indexes (not update - rebuild). Whenever I make any changes to indexes, I simply run my Create_index_rebld() function which checks the index definitions in each table and creates (or recreates) my "Index_rebuild" script with all the latest index definitions. (It takes less than 5 seconds for about 30 tables with a total of about 60 indexes and works on any application.)

          Then, I just put a button on my maintenance menu to start the Index_rebuild script whenever needed - whether indexes are missing or corrupted. The script even has options to select which tables to rebuild or to ignore. (I.e., either "rebuild these 3" or "rebuild everything except this one.")

          The thing I like about my method is that it doesn't rely on keeping backup files around.

          Another method I've heard of involves keeping the index definitions in a table. This makes it easy to add and delete indexes as necessary by just putting a new "index definition table" in the database and running a "rebuild" routine that reads the definitions from the table.

          Cal Locklin
          www.aimsdc.net

          Comment

          Working...
          X