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



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

numbers on compact

  • Filter
  • Time
  • Show
Clear All
new posts

  • numbers on compact

    Stupid question # 39467
    On doing a database compact, what do the numbers on the status line refer to?
    I have 51 dbf's
    I did a compact and on the status line was "20 20"
    I did it again and it changed to "7"

    I have no idea what it is, anyone know?


  • #2
    RE: numbers on compact


    This is just based on observation. I believe the numbers represent index tags processed and records processed/(records before pack, after pack). The order in which the tables are processed is beyond me. A change in the order might yield different final numbers in the status bar.
    There can be only one.


    • #3
      RE: numbers on compact

      thanks Stan
      You might be right, but most of my dbf's are a lot more than 7 or 20 records. The last one (if compacted alphabetically, which is how they are displayed) is a zipcode dbf with about 45000 records. I guess it doesn't really matter, I was just curious.



      • #4
        RE: numbers on compact


        I tend to agree with Stan. I frequently compact to see if I've written code sufficient to clear a form or be sure to have unloaded a table. It's got to be indexes or something like that. For instance, I have a single table on a new project and it has 4 records and 1 index. When it compacts I can see a '1' and a '4' blink by.

        Mmmmmmmmm....... Stan might be on to something, Eh?

        Ken the newbie.


        • #5
          RE: numbers on compact

          I you want to test my theory, duplicate one of your larger tables to your application directory, create several index tags, create a new "code" script containing the following:

          error = .F.
          on error goto error_msg
          tbl ="c.dbf",FILE_RW_EXCLUSIVE)
          if .not. error
          ui_msg_box("Finished","C.dbf has been packed.")
          end if

          errnum = error_code_get()
          err = str(error_code_get())
          ermsg = error_text_get()
          CASE errnum = 1000

          CASE errnum = 1002

          CASE else
          ''ui_msg_box("Error",ermsg+" "+err+" "+name,UI_ATTENTION_SYMBOL)
          ui_msg_box("Error","The following was in use or missing "+name,UI_ATTENTION_SYMBOL)
          error = .T.
          resume next
          END SELECT


          Change the "c.dbf" above to the table you have duplicated. When the script is run and finished, wait a few seconds and you should see numbers in the status bar representing the number of records processed for each of the indexes. IOW if you have seven records and 4 indexes, in the table in question, you should see 7 7 7 7 in the status bar.

          When you compact the information is overwritten for each table processes, of course. I know Alpha doesn't use alphabetical order for table processing during compact. I'll investigate and see if I can figure that out.

          There can be only one.


          • #6
            RE: numbers on compact

            Hello Ken,
            Searched for "clear a form" and found your remark, can
            you share with me your technique for clearing a form?

            I have a method in place for a very simple add-mode-only
            form, but can't get the same principle to work on a more
            complicated form (this form has change-mode, and add-mode
            going on simultaneously) via a one to many situation where
            the (one) is a master of sorts that must be "looked-up" and
            displayed before child (many) can be added. The master
            is subject to changes, but the children will usually be added. This is a form with an embedded browse for the child records.

            Would like to start the form with all (one)or (master) info
            blank, but it seems that good ol a5 wants to assist me by
            dropping the first record that it finds onto my form, even
            before I begin a look-up.

            I'm sure there is plenty of information on this forum on the subject, but can't seem to find it.

            Advance thanks to you, and all potential repliers.


            • #7
              RE: numbers on compact

              The trick to do that is to create a new record with xbasic, but don't add any data. Then fetch that blank record. You may have to modify your field rules though, to get this to work logically for you. Another more complex method is to use a form with only variables - then save those values to the table.

              AlphaBase Solutions, LLC

              [email protected]


              • #8
                RE: numbers on compact

                Thanks Peter, I was afraid it might be something like that,
                guess I'll just live (or die) with it. Grumble, grumble.