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

Packing Problem

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

  • #16
    RE: Packing Problem

    does this happen to every table, or just one? you may have corrupt data in one of your tables, if it is occurring in just one table. try appending records from that table to a duplicate of the table with the same table structure, and see if you can pack the duplicate.

    Comment


    • #17
      RE: Packing Problem

      Another action to try would be to open the indexes for changes or updates in each table, that would tell if you're getting an exclusive open to each table. If you can use Alpha to copy the tables without the data dictionary to another directory and then pack it there, you would know that the problem may be in the data dictionary and not in the table. You might also try this with and without indexes to see those results.

      Dave

      Comment


      • #18
        RE: Packing Problem

        Peter,
        This happens to every table and set.
        i just ran Norton utilities and scaned for virus's, every thing ok.
        I deleated the build [email protected]!% and then down loaded again and re installed again.
        Same thing as previous.
        I am really stumped.
        Al

        Comment


        • #19
          RE: Packing Problem

          Al,

          Zip a copy of one of your tables and post it here. That will give us a chance to verify whether or not it is corrupted.

          -- tom

          Comment


          • #20
            RE: Packing Problem

            one last thing you could do is to create a new, empty database, and attach one of your tables to the empty database and see if you can pack it.
            if not, you probably have some conflicting .dll or other program on your computer. i am using winxp home edition and have no troubles packing tables with build 1215.
            one thing you didn't describe when you said you right-click on the table and choose "pack". do you get a message that warns you that packing will permanently remove all deleted records, or does your error occur before that? if you don't get that error message, then you probably have an outdated version of the system.aex file in your a5v5beta directory.

            Comment


            • #21
              RE: Packing Problem

              Peter

              I do get the warning sign first.
              I will try your other suggestion also.

              As to try to zip up a table and post here. I cannot do it because I get the same message as the first thread "smartheap library - mem_bad_pointer"

              Al

              Comment


              • #22
                RE: Packing Problem

                Al,

                Does your table contain memo fields?

                Have the memo fields grown to unusual sizes?

                -- tom

                Comment


                • #23
                  RE: Packing Problem

                  Tom

                  No and no

                  Al

                  Comment


                  • #24
                    RE: Packing Problem

                    Al,
                    Close A5 and open an explorer window and do a file search on *.muf files. Delete all of them. Try your pack again.

                    Comment


                    • #25
                      RE: Packing Problem

                      Al,

                      You might try installing your database on another computer different than the first and see if it has the same problem. You would then be sure this is not a hardware issue.

                      The other thing to do is to start with a simple database which you can pack successfully, then add tables, indexes, forms, reports, and finally field rules to see what breaks the successful packing conditions. You can then remove this portion of the database, save the working database, and try rebuilding the bad portion in a way that works. If the cause is a corrupted object, deleting it and building a new one likely will solve your problem.

                      Dave

                      Comment


                      • #26
                        RE: Packing Problem

                        Al,

                        Feel free to email one of your tables to me. I'll safeguard your privacy, and will let you know whether I can pack it here.

                        -- tom

                        Comment


                        • #27
                          RE: Packing Problem

                          Are you using a startup form? If so, with V4.5
                          you would have to change the database properties to not
                          run the form on startup to compact the database.

                          Comment

                          Working...
                          X