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

Need to compact database

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

    Need to compact database

    I am finding that I need to compact my database almost at all times when I delete a child record in a 1 to many set (my reports come out incorrectly without the compacting taking place). My need to delete a record is required, but from the readings, I was under the impression compacting was mainly necessary during development and not during actual use.

    I don't do anything fancy with the delete, using an Action Script to delete the child record. I leave the parent record in tact (I do not want to delete it).

    Can anyone suggest what I am missing, please?
    "Ollie, remember how dumb I used to be? Well, I'm much better now."

    Pete

    #2
    Re: Need to compact database

    You haven't told us what "my reports come out incorrectly" means. Among other things compacting rebuilds indexes, if I recall correctly. Might your misbehaving reports be the result of corrupted indexes? What index expressions are used to link records in the set? What index expressions are used in the report? You wouldn't be using filtered indexes by chance? More details. Or a sample database for us to examine. Would help us help you.

    In the meantime, try rebuilding your indexes instead of compacting the next time you have the problem.

    Comment


      #3
      Re: Need to compact database

      Tom:
      Thanks for getting back to me so quickly. Clarifying reports output....wrong individual (child) coming up in parent file. Once I compact child and parent are then properly connected again.

      Ah, indexing, an area that I am pretty clueless on, as in my previous life of using flat databases, I had no requirement for their use. So let me start reading up on indexing and see where I am going wrong in that area. I am guessing that the only indexing that is going on is the one Alpha creates for me automatically when I create the initial auto-increment id field, with one exception. I did create an index that Gabriel used in generating an order routine in a report (found that in another thread that I believe you also read.)

      Code:
      dbsum("results","Sum",Results->Eventathid,"Points")
      "Sum" is the name of the index and is based on Eventathid (a character field of 6 spaces that is a child field filled by using a lookup to the parent field id, thus creating a link between parent and child.

      However, it isn't only the report where I see the incorrect parent-child connection. I sometimes also see it in a form with an embedded browse- correct parent, wrong child. So, I am thinking that something goes out of synch with the parent-child link when I delete a child. At least one child ends up linking with a different parent. Once I compact, all children are correctly linked to their rightful parent. Maybe it's part of "Trading Places"....

      I will take a closer look at indexes and see if I can understand that area better.
      "Ollie, remember how dumb I used to be? Well, I'm much better now."

      Pete

      Comment


        #4
        Re: Need to compact database

        Pete,
        I was under the impression compacting was mainly necessary during development and not during actual use.
        True.
        Instead of Compacting the database, I think most would just Pack the table in question--which I have read will also rebuild the indices.
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Need to compact database

          Mike:
          Hmm, another new concept that I don't think I really caught on to. For some reason I thought compact and pack were the same. More late reading for me.

          Thanks for your thoughts on this....

          Here is what I find for compact: The A5.COMPACT() method compacts the current database. This rebuilds all indexes, removes all deleted records and reclaims unused space in all dictionaries and memo field files.



          This is what I found for packing: Packing a table reclaims the space taken up by deleted records and rebuilds indexes.

          Not sure if there is a difference and how it would affect what happens with my problem of parent child separation.
          Last edited by trackmanpete; 01-21-2009, 01:16 AM. Reason: Did some reading
          "Ollie, remember how dumb I used to be? Well, I'm much better now."

          Pete

          Comment


            #6
            Re: Need to compact database

            Pete,

            Don't know if this helps but I have a button on my Main Menu which I press to pack all the tables in just one click. If you use the Genie to create an onPush event for the button then pick "Pack" and either select "All tables in Database" or "Selected tables" and tick each table you want to pack. When you press the button each table you selected will be packed - its that easy!

            Comment


              #7
              Re: Need to compact database

              Alastair:
              Thanks for your suggestion. I have seen that option. My concern is/was that I was doing something wrong when deleting to cause my problem of links no longer being connected properly after I do as few as five deletes of children records. In an Access commercial database I use, they also have a Pack button, but I have never needed to use it, but then I haven't deleted many entries there, either.

              I guess I am trying to figure out if there is something I should include in my code when I delete a child record, so that another child from another parent doesn't show up. That is what happens on occasion now. Once I compact or pack everything links up properly.

              I did go into the database and rebuilt my indexes, but I do need to do more reading on how they are created and what they do...

              Thanks, again.
              "Ollie, remember how dumb I used to be? Well, I'm much better now."

              Pete

              Comment


                #8
                Re: Need to compact database

                Pete,

                PACKing a table will physically remove records previously marked for deletion (deleted). It rebuilds indexes. It does nothing to the DICTIONARIES for the table.

                COMPACTing will do much more.

                In my experience COMPACTing should never be necessary for an application that's been released. It's useful during development because it cleans up the dictionaries which store all your layouts, field rules, and scripts. Depending upon the requirements of the application PACKing should be rarely needed, too. Something you might do on a monthly or quarterly basis, perhaps, as part of regular maintenance.

                It seems to me you have an indexing problem and I am glad you will be investigating it. Ordinarly, deleting a child table record should not corrupt indexes.

                Comment


                  #9
                  Re: Need to compact database

                  Tom:
                  Thanks for your insight. I just read Cal's viewpoint on packing and indexing where he is saying what you are. I will continue to investigate how corruption of indexes might occur and see if coding is not working correctly to see if I can come up with an answer. There is still a foot of snow outside and temps are in the teens, so I have plenty of time to research...
                  "Ollie, remember how dumb I used to be? Well, I'm much better now."

                  Pete

                  Comment

                  Working...
                  X