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
Devcon 2020 Goes Virtual! LEARN MORE >

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

ddm modifying???

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    ddm modifying???

    Hi all,

    I have had the need on a few occasions to view/modify the .ddm file of a table.

    I know/think it was covered somewhere, but does anyone remember the procedure to access a ddm file?

    Thanks.
    Dave
    Tags: None
    #2
    RE: ddm modifying???

    David

    What exactly are you trying to do with the ddm file? It is part of the table data dictionary and modifying it will probably totally corrupt the data dictionary and make the data dictionary useless.

    Jerry

    Comment

      #3
      RE: ddm modifying???

      jERRY,

      I have a very large form that has several fields unused and are not in the form. When I remove the unused fields from the very large table, the form gives me an error message and when i check it out, it is the fields I deleted from the dbf file. they are truly not in the form though.

      Dave

      Comment

        #4
        RE: ddm modifying???

        With all due respect,

        I really would like to know how to access this file. I can open it in word, but it seems to be jumbled and not very well laid out to an outsider. there is no clue as to its real file type.

        Dave

        Comment

          #5
          RE: ddm modifying???

          While not on the form they might still be referred to in calculated fields.

          Simply add the fields back to the .dbf, even if only one character text fields, by the names that they originally had, edit the form, find and remove the references, then you can safely remove them from the .dbf.
          There can be only one.

          Comment

            #6
            RE: ddm modifying???

            If you are determined to try to access this file, go to the Alpha Software site, select newsletter, and open issue 5 (July 2002). In that issue, I discussed what each file type does. The ddm is a memo file that contains the form design in a proprietary format and is attached to the ddd and ddx files. You certainly can access the ddm with a file viewer program, but trying to edit a form design here is a recipe for disaster.

            You problem may be what Stan suggested or another problem. I once had a form where I had used cut and paste to add objects to a conditional object. The problem was that cut and paste added duplicates of the fields that were hidden. When I removed the fields visible, I though I had found all of the fields. However, the "hidden" fields were still referenced by the form and could not be found on the form.

            The solution to this problem took a couple methods. In one case, compacting the database fixed the problem. In another, I added the fields back to the form on a blank area of the form, saved the form, compacted the database, reopened and deleted the fields I just added. Now all references to the fields were gone. Unfortunately, in one case I had to recreate the form from scratch, which was a real pain. I learned not to cut and paste onto conditionals or tabs subforms.

            By the way, in one case I did go into the ddm file and look for references to the "hidden" fields - there were none. The problem seemed to be some form of corruption between the memo information and the other form design information in the ddd file.

            A5V5 seems to have eliminated this problem. This is not an issue that anyone has mentioned on the V5 forum. It was very rare in previous versions.

            Jerry

            Comment

              #7
              RE: ddm modifying???

              Jerry, Stan,

              Thanks.

              I have tired all the methods you described and maybe a few more and have messed up the ddm, ddx, and ddd files(smart enough to make copies).

              The only solution was to remake the form. It even messed up when redone with the same name, so I had to give it a new name too. Problem is solved, but not fully understood. I hate note understanding a problem.

              Thanks again.
              Dave

              Comment

                #8
                RE: ddm modifying???

                David

                I agree that no knowing the cause can be worrying. Unfortunately, corruption problems as so named because they are somewhat unexplainable. Recently I ran into a problem helping another user that was completely bizarre. Between the 2 of us, we couldn't determine any action that could be linked to the end result. A database data dictionary became corrupted in a way that made no sense whatsoever.

                The good thing is that many of the consequences of problems are avoidable. The usual precautions like backup regularly, keep multiple copies, document what you are doing, test every change, and more, will minimize the probability of a serious problem.

                I may sound like a broken record, but regular compacting seems to be one of the most helpful things to keep everything working well. Many users do not realize that even a simple change in a form design leaves both the new design and the old design saved in the data dictionary. The old design appears to be marked for deletion, just like a deleted record. And just like a deleted record, it must eventually be removed. Since the information for the design is saved in memo form, not cleaning it up from time to time can lead to so big headaches. Nearly every "unexplainable" corruption I have seen has had one common thread, a failure to compact on a regular basis. I once saw a data dictionary that had a single form and was a few megs in size that dropped to less that 200 kb when compacted. That is a lot of "junk"

                Glad you got the form working. Sorry we couldn't come up with a better way to get there.

                Jerry

                Comment

                Previous template Next
                Working...
                X