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

end user compacting procedure

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

    end user compacting procedure

    OK -- all the books say make it easy for end users to pack, compact, repair indexes, etc....
    How do you do a 'compact' from a form in the db and still have all the 'forms', 'operations', 'and such' CLOSED??????

    I keep getting 'drop table' requests and want to eliminate the possibility of the end user dropping one of the req'd tables accidentally...

    Comments pls??
    D

    #2
    RE: end user compacting procedure

    I have a utilities menu that is based off a dummy .dbf and when you go to the utilities menu it closes all other windows. One of the buttons is a re-index data and another is the pack database, works great. I do exclude the packing of the utility dbf, of course.

    Comment


      #3
      RE: end user compacting procedure

      thanx John..
      I have no problem with the index repair or packing tables.
      The only problem is with compacting the db. Because the menus are based on a small set, they keep 3 tables open:
      One is the dummy dbf for the menus and the other two are one record tables that hold 'owner' and 'user' data.
      When compacting, these three are "not" and A5 asks if they should be dropped.
      I have a msg box that says "don't drop any tables", but I don't like the fact that the question is even asked.
      Just need to find out how to work around it or disable it...
      D

      Comment


        #4
        RE: end user compacting procedure

        Richard

        Once a program is developed, there is no need to compact. Compacting only effects the data dictionaries, which in a final product, should not be changing.

        However, it is possible to create a manual compacting procedure. You can use table.compact() to compact each table and the adb. Create a script that first creates an array of all tables and sets in the database. Then eliminate the current table and add the adb for the databse. I run the script from a main menu table that doesn't need to be compacted. Loop through the array and compact each table. In fact, the help file has a sample script for one table that could be modified easily.

        I include the utility in an application "just in case". If there is a crash or other anamoly, I may direct the user to run the compact. It probably won't have any effect, but it doesn't hurt.

        Jerry

        Comment


          #5
          RE: end user compacting procedure

          Ok, will eliminate the 'compact db' from the menu choices...... I kinda felt that this would have to be the case, but I needed to get more input...
          Thanx
          D

          Comment


            #6
            RE: end user compacting procedure

            Jerry,

            I think Database Compact will pack all the tables, too.

            -- tom

            Comment


              #7
              RE: end user compacting procedure

              It will, but I prefer to split the actions. I update the production indexs and pack in separate actions. It is faster to run only one action and gives the option to just pack or update indexes on just one table.

              Jerry

              Comment

              Working...
              X