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

Compacting the.ddm files

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

    Compacting the.ddm files


    There are some previous topics relating to maintenance of data dictionaries, but I'm still not clear on the following.

    When doing database compact, or using the xbasic command database.update("*.ddd")it does not seem to bring down the size of the .ddm file.

    In A5 V1 the application maintenance operation used to reduce the size of these files.

    Does anyone know how to compact .ddm files in A5 v4.5?

    Thank you

    #2
    RE: Compacting the.ddm files

    Rob

    I think the command is dd_update(".ddd")
    Al Buchholz
    Bookwood Systems, LTD
    Weekly QReportBuilder Webinars Thursday 1 pm CST

    Occam's Razor - KISS
    Normalize till it hurts - De-normalize till it works.
    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
    When we triage a problem it is much easier to read sample systems than to read a mind.
    "Make it as simple as possible, but not simpler."
    Albert Einstein

    http://www.iadn.com/images/media/iadn_member.png

    Comment


      #3
      RE: Compacting the.ddm files

      OK, I did that, and the .ddm file is still much larger that it used to be when using A4v1, where it was 127,000 bytes

      The database only contains 4 fields, a couple of lookups, and 4 short scripts, and it won't reduce from 354,294 bytes.

      Seems to be larger than it should be.

      Any ideas???

      Comment


        #4
        RE: Compacting the.ddm files

        Rob

        A5V4 is a more complex program than A5V1. Actually, that size doesn't seem very large depending on the complexity of the forms and other designs. The table database dictionary files (ddd, ddm, ddx) contain all form designs, browse designs, labels, etc. Table data (and most structure information) is contained in the dbf and fpt files and indexes are in the cdx files. Scripts are contained in the Database data dictionary files (alb, alm, alx)

        You don't have to use code to compact the data dictionaries. Just go to the File option on the menu and scroll down to Database Compact and select that. It will compact all of the data dictionaries. That includes all table dictionaries and the main database dictionary.

        Jerry

        Comment


          #5
          RE: Compacting the.ddm files

          Actually, I just checked one of my applications with a table with a number of fairly complex forms and the ddm is over 1 meg. A couple others are nearly that large.

          Jerry

          Comment


            #6
            RE: Compacting the.ddm files

            Mine contains a single data entry form, with a sub-form, and two reports, all based on just 8 fields.

            I looked at the .ddm file, and it contains information on a list lookup I haven't used for years.

            In looking through the v4.5 one, it seems to contain references to V1, I wonder if it's trying to save duplicate information from when I imported the file from V1

            Comment


              #7
              RE: Compacting the.ddm files

              Rob

              Conversion form A5V1 to A5V4 does work ok, but seems to leave much legacy information. You could try duplicating the table in A5V4 and see if the duplicate is as large, or recreate the new form in A5V4. Either may reduce the size.

              Jerry

              Comment

              Working...
              X