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

ALM corruption; no memo files

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

    ALM corruption; no memo files

    I have a database that continues to corrupt the ALM file (it grow to a huge size and creates a $$M file) and delete the ALX file every time I compact it. There are no forms, reports, or anything else other than tables, scripts, and functions in the database (it is a web database). None of my tables has even a single memo field (i.e. there are NO memo fields). Why does this happen and how do I fix it?

    Howard
    Howard G. Cornett, Independent Consultant

    #2
    RE: ALM corruption; no memo files

    The fact that it's a web database shouldn't be making a difference here.

    Maybe try copying the .alb, alm and alx to another name. In DOS:

    copy original.alb temp.alb
    copy original.alm temp.alm
    copy original.alx temp.alx

    Then rename all the temp.al* files to your original database name.

    You can also rename the files to make a .dbf that you can look at, and see what record(s) look trashed:

    Copy original.alb temp.dbf
    copy original.alm temp.fpt
    copy original.alx temp.cdx

    Then add the table to your database and browse it for a looksee. If you find stuff that doesn't look like it belongs there, delete the record, pack the table, then reverse the naming immediately above.

    I don't need to remind you to make a good backup first, right?

    - Steve
    -Steve
    sigpic

    Comment


      #3
      RE: ALM corruption; no memo files

      Hello Howard,

      "" have a database that continues to corrupt the ALM file .... and delete the ALX file every time I compact it.""

      The alm is a memo file. If you are saying that everytime you try a compact, it fails, then you have a corruption problem and it has never been fixed so if you continue to try to compact, it will continue to give you the error. You must first 'fix' the corruption. To fix this, I'd start by copying and renaming the files as normal dbf files and related dictionary files. Add these to a database and run Alpha's TablePointer.memo_check() routine against it and see if you can't fix it. Then copy the files back and rename them. There are other approaches as well as a third-party tool or two to address this.

      If you are say that you have fixed the corruption but it still continues to get re-corrupted...... I don't have a good answer for you.

      Good luck,
      Jim

      Comment


        #4
        RE: ALM corruption; no memo files

        The alm is a database data dictionary, not a table data dictionary. About the only things saved there are the scripts, functions, menus, etc. You could try removing all of the database properties and see if that helps. Be sure there are no "legacy" libraries attached. If you changed the name of the database at some point, you will typically find the original database name linked as a library. If it no longer exists, that can create some odd behavior.

        If none of that works, the only solution may be to create a new database (adb) in the same folder and move the existing tables, sets, scripts, etc to the new database.

        Avoiding corruption like this is one reason to compact on a regular basis when you are designing and making changes to the structures. And keep good backups.

        Jerry

        Comment


          #5
          RE: ALM corruption; no memo files

          Hello Jerry,

          Yes, I shouldn't have said dictionary file. What I was trying to convey is:

          rename the *.alb to *.dbf
          rename the *.alm to *.fpt
          rename the *.alx to *.cdx

          Now you can deal with it as a regular table to fix the corruption. The *.alm is the memo file.

          Thanks,
          Jim

          Comment


            #6
            RE: ALM corruption; no memo files

            JIm

            That might work, but I have never had much luck fixing memo fields. The problem with a data dictionary is that there are aren't many "records" and even if you can find which menu, script or whatever is causing the problem, you may not be able to fix it without scrambling everything else. However, a good backup would work.

            Jerry

            Comment

            Working...
            X