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

Compound Index Error

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

  • Compound Index Error

    I have been running the same application for years and this is the first time I have seen a error message when trying to open a dbf file. I was trying to open this file because it is no longer showing a drop down list when I click a form location for that particular dbf. This function is fine for other dbf's but not the one. The dbf name in Mon.dbf. It is part of a set that a calendar is built on which contains a header file, cal_hdr.dbf, and links to the days; Sun.dbf, Mon.dbf, Tue.dbf, Wed.dbf, Thu.dbf, Fri.dbf and Sat.dbf. Go figure! They all have the same link.

    Anyone know what may have caused this error to just show up and more importantly, how to correct it?

    Thanks,

    Gene

  • #2
    Re: Compound Index Error

    I had an issue where the posting didn't go to script.Suggest you compact and try again.
    It fixed my issue.
    Ted Giles
    Example Consulting - UK
    .

    sigpichttp://ec12.example-software.com//
    See our site for Alpha Support, Conversion and Upgrade.

    Comment


    • #3
      Re: Compound Index Error

      Thanks for the suggestion Ted. When trying to pack Mon.dbf, an error message is returned. Could not Pack or Rebuild indexes for mon.dbf Dictionary.

      Comment


      • #4
        Re: Compound Index Error

        Gene, it may be helpful if you were to post the complete error message.

        Is this running on a stand alone machine, or over a network?

        Do all workstations encounter the same error?

        If you close alpha on all workstations except the one containing the developer version, can you rebuild indexes for this table from the control panel?

        If not you may have a corrupted table on your hands, in which case Alpha can't sort the records using your index tag definitions.

        Does this table contain memo field data by any chance?

        Comment


        • #5
          Re: Compound Index Error

          Hi Tom.

          This is a stand alone PC running Windows 10. This machine has the developer version. No memo fields.

          I think that answers the questions. It appears that I am going to have to recreate everything that is based on Mon.dbf. Gulp!

          Well, it's a long weekend.

          Is it possible to identify all A5 files that pertain to Mon.dbf so that I could do a restore without those? Or are things intertwined in A5 such that I can expect to lose my data?

          Gene

          Comment


          • #6
            Re: Compound Index Error

            Gene, I would copy the entire project to a separate directory and do the experimenting in the new directory.
            The other thing I would do is start looking through recent backups to get the latest working version.

            Comment


            • #7
              Re: Compound Index Error

              To all concerned, I have it working again by being somewhat creative. Here are the steps I took. If anyone can shoot a hole in this plan, please let us know.

              1. Copy the directory that has my application to a safe directory
              2. Open the application and create a new dbf (I called it Monday)
              3. Write a short program to copy the contents of Mon to Monday
              4. Close A5 and working in Windows, change the name of every corrupt file (in this case, Mon.CDX .DBF .DDD .DDM and .DDX) to xMon.CDK etc.
              5. Rename every Monday file to Mon
              6. Open the application.
              Something curious happened here. A5 was looking for Monday.dbf! So I changed the name of the original Mon.dbf (not the other extensions) from xMon.dbf to Monday.dbf
              I wonder what behind the scenes is looking for Monday.dbf and apparently not any other extensions??
              Anyway, the application opened just fine with no apparent problems after putting the useless Monday.dbf in the directory.
              7. Update the field rules for the new Mon.dbf.

              Everything seems to function fine and I lost no data!

              Creativity, creativity, creativity!

              Gene

              Comment


              • #8
                Re: Compound Index Error

                Gene,

                I like Gregg's idea of creating a separate directory and experimenting there first.

                If the table is corrupted that does not necessarily mean the related dictionaries are corrupted also. The DDM, DDD, and DDX files for the table contain your field rules, forms, reports, etc. Maybe they're not corrupt and its only your "data" that is misbehaving.

                The first thing I'd try in my "sandbox" experimental directory would be to simply copy in a good backup copy of the DBF and CDX files for the table. Then test to see if it works correctly, wherever the table is used in your application.

                LATER EDIT to this post: I see now that you have it working. Not sure I understand all that you did but I'm glad you succeeded.

                -- tom
                Last edited by Tom Cone Jr; 04-03-2020, 09:22 PM. Reason: Cross-posted with Gene.

                Comment


                • #9
                  Re: Compound Index Error

                  Always nice to see something work the way we hope it will.

                  Comment

                  Working...
                  X