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

corrupt index in a set in Win 2000 pro

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

    corrupt index in a set in Win 2000 pro

    I have a set consisting of 2 tables
    1.job details
    2.job status history
    linked on a job id number in the job details on a one to many link no referential integrity in descending order.
    The job id number is auto increment in the details database.

    Job details database has 2 indexes
    1. jobid (unique)
    2. name

    I have this set on a network with about 5 other systems which are running runtime and the shadow of the "real" database.
    Files are stored on a Windows 98 machine (my so-called server)
    I just upgraded 3 of the workstations to Win 2000 pro
    1 workstation is WinMe
    1 workstation is Win98SE

    The Win 2000 machines corrupt the indexes in the details database in as few as 1 record and sometimes in as many as 10 records. The other 2 workstations (Me and 98) work just fine.

    I get the message that "your indexes may have become corrupted....etc" as soon as you try to save the new record.

    All systems are running patch 1506_1058.
    Am I missing something in Win 2000? Why does it only happen on those running Win 2000?

    I have tried wiping out the indexes and re-defining them, and even went as far as deleting the .cdx file the re-defining the indexes...nothing seems to fix it.

    Dan
    Fraser Optical Inc

    #2
    RE: corrupt index in a set in Win 2000 pro

    There was another thread about this kind of problem recently. Without seeing your index definitions I'm not sure if the solution from there would fit your situation. But it's possible that if you get rid of the name index temporarily, the problem will go away. If it does, you may be able to come up with a permanent fix by changing the way the name index is defined.

    Finian
    Finian

    Comment


      #3
      RE: corrupt index in a set in Win 2000 pro

      I read that thread and tried virtually all the suggestions.
      no luck
      It has only been happening on Win 2000 pro machines.

      Any other suggestions?

      Dan

      Comment


        #4
        RE: corrupt index in a set in Win 2000 pro

        Might this be related to the issues discussed in other threads concerning opportunistic locking and disk caching on the server or workstation?

        -- tom

        Comment


          #5
          RE: corrupt index in a set in Win 2000 pro

          What are the index definitions?

          Finian
          Finian

          Comment


            #6
            RE: corrupt index in a set in Win 2000 pro

            Tom
            I tried to find the threads your speaking of and couldn't exactly pinpoint them. Maybe a link would help me find them.

            Dan

            Comment


              #7
              RE: corrupt index in a set in Win 2000 pro

              Try this link

              http://msgboard.alphasoftware.com/alphaphorum/read.php3?sortby=lastreply&direction=desc&num=11&id=67770&thread=67682

              Jerry

              Comment


                #8
                RE: corrupt index in a set in Win 2000 pro

                Trying those suggestions,will see what happens

                Thanks
                Dan

                Comment


                  #9
                  RE: corrupt index in a set in Win 2000 pro

                  sorry for the delay, was on vacation

                  jobid ascend unique
                  name= trim(lastname)+" "+trim(firstname)

                  pretty simple definitions.

                  Dan

                  Comment


                    #10
                    RE: corrupt index in a set in Win 2000 pro

                    Dan,

                    The Unique key word behaves differently than many folks think. It does not enforce unique key values in your table, for example.

                    -- tom

                    Comment


                      #11
                      RE: corrupt index in a set in Win 2000 pro

                      I have given up on Win 2000 issue, this database is in production 10-12 hours a day and I can no longer afford to re-build my indexes every 5 records on average.

                      My only other solution may be to totally rebuild the entire database from scratch as something else must obvoiusly be wrong.

                      The other solutions with oportunistic lock etc. didn't help.

                      Thanks for all the suggestions.


                      Dan

                      Comment


                        #12
                        RE: corrupt index in a set in Win 2000 pro

                        I know you're ready to give up (or maybe already have?) but try this: change the name index definition to

                        trim(last)+" "+trim(first)+" "+jobid

                        I don't guarantee a fix, but I'd say it's at least an even shot.

                        Finian
                        Finian

                        Comment


                          #13
                          RE: corrupt index in a set in Win 2000 pro

                          Dan,
                          I don't think anything is wrong with your database design, rather, your server is the issue. I experienced index corruption problems every couple of days when I added WinXP workstations to a network in which a Win98 machine was acting as the file server. I jumped through hoops rewriting code and redesigning forms, and although simplifying the application and minimizing the use of sets in data entry helped, the problem was only really solved when I upgraded the server. Currently I have a Linux-based server and have not had to rebuild an index in the 8 months since I deployed it. If you don't want to go to Linux you can probably manage with a WinXP Pro server (WinXP Pro will support up to 10 network users), or if your network has only 5 workstations, WinXP Home (which supports up to 5 connections), but I would most enthusiastically recommend Linux. Once you set it up you can forget about it.
                          - Peter

                          Comment


                            #14
                            RE: corrupt index in a set in Win 2000 pro

                            Peter,

                            I don't have a dedicated "server" however I use a win 98 machine to "store" all the data files in a peer to peer network. You think that still may be an issue?

                            I do have other databases that run correctly with the 2000 machines, however the data entry is minimal on those databases. The database having problems has the most used, and most entered data records, almost constant throughout the day.

                            Dan

                            Comment


                              #15
                              RE: corrupt index in a set in Win 2000 pro

                              Dan,

                              What other tasks are you running on your server? Please realize that if something running hiccups or hangs up, your network users can have serious problems. We use WinNT and Win2K as dedicated servers. I would suggest that if you can, switch one of your win2K machines to be the server. We have win98, winXP, and win2K workstations, and have not encountered anything like you are describing.

                              Again, if you have the hardware, I would recommend a dedicated server.

                              Tom

                              Comment

                              Working...
                              X