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

Memo fields

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

  • Memo fields

    Ah yes, another post about Memo fields. Is there an INDEX for memo fields that can be rebuilt? Where are the memo field information kept? Since a memo field is just a pointer really, where are the memos..really.

    I'm thinking about this because I have a memo field that on its own will switch memos between disparate records. Now isn't that interesting? How can this occur and is there any solution..other than not using memo fields?

  • #2
    Re: Memo fields

    back end database type? i.e. dbf, ms_sql, mySql, ???

    Comment


    • #3
      Re: Memo fields

      Oh, it's DBF..native Alpha.

      Comment


      • #4
        Re: Memo fields

        Dennis

        There is extensive discussion about memo fields on this board and on other venues. A search engine will help you find a wealth of information.

        One of the primary design flaws with memo fields is a lack of a two way pointer. There is only one pointer from the data record to the memo field value. So when that pointer is corrupted, there is not a way to rebuild. (at least not an automatic way)

        A distinct advantage of an SQL database is the controlled commit that is more solid than a dbase update.

        That said Murphy will strike both types and cause problems - perhaps at a different rate.. (I'm still waiting for perfection.. it'll be a long time coming.)
        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


        • #5
          Re: Memo fields

          That answered my question. And I see the container for the memo field is in the DBF itself--not wise. If I were redesigning, I'd create a child 'memo' table. Live and learn.

          Comment


          • #6
            Re: Memo fields

            Yes, using a child table linked 1:1 for your memo field data is smart.

            There's a useful article at www.learn alpha.com called "Memos and Browses that work", or some such. Has proven invaluable to me.

            There's also a relatively new method for the TBL object in alpha that may be of some help. Check here.

            Comment


            • #7
              Re: Memo fields

              Originally posted by Dennis Mathias View Post
              That answered my question. And I see the container for the memo field is in the DBF itself--not wise. If I were redesigning, I'd create a child 'memo' table. Live and learn.
              Actually the pointers for the memo field are in each record in the <tablename>.dbf, the memo field data is stored in the <tablename>.fpt file.

              The pointer indicates the starting block within the <tablename>.fpt to locate the memo data.

              As always, Tom Cone has provided additional helpful information.
              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


              • #8
                Re: Memo fields

                This is helpful! So, I looked at the FPT file with notepad and sure enough the info is in there! Now, how to get it out. Do you suppose this is just a DBF file re-typed? If I could import that, I would loose no data. Then I could do a one-to-one link to a table that has memos in it. This is real help! And BTW, I did look around for some inside information like this..never was really satisfied. Now I need to find out what an FPT is. Probably not DBF because the field length would not be static. Must be some sort of START-STOP codes. Little beyond me at the moment. But, seriously, THANKS!

                Comment


                • #9
                  Re: Memo fields

                  There are utilities available to fix memo linkage problems.

                  One is Dsalvage

                  They require that you manually reset the pointer to the proper block address for the memo data.

                  It's a long and tedious process.

                  How many records are in your application?

                  When was the last backup done that has no memo problems and how much data has been entered since?

                  The answer to these and other questions ($) will help you determine the solution path for you.
                  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


                  • #10
                    Re: Memo fields

                    We have about 6000 records in the parent and maybe 15000 children. We don't know when the memo issues occurred but we're noticing them now.

                    Comment


                    • #11
                      Re: Memo fields

                      Not that it helps you, but memo field corruption is unheard of in the sql world as far as I know. Also, a Visual Foxpro developer-friend of mine who has used VFP every day for 20-years says he has never heard nor seen memo field corruption in VFP. Of course VFP isn't using dbfIII either, but it does use dbf. Just stating this as a point of reference.
                      Peter
                      AlphaBase Solutions, LLC

                      [email protected]
                      https://www.alphabasesolutions.com


                      Comment


                      • #12
                        Re: Memo fields

                        Actually, by accident I have found a memo rebuilder (sort of) embedded in A5V11. There is a "Check/repair memo fields..." under "Utilities" which you can display by right clicking on your {table} in the Control Panel. Just what I wanted! I came across this accidentally although it doesn't seem to be mentioned in the documentation.

                        Comment


                        • #13
                          Re: Memo fields

                          Originally posted by Dennis Mathias View Post
                          Actually, by accident I have found a memo rebuilder (sort of) embedded in A5V11. There is a "Check/repair memo fields..." under "Utilities" which you can display by right clicking on your {table} in the Control Panel. Just what I wanted! I came across this accidentally although it doesn't seem to be mentioned in the documentation.
                          did it fix your problem?
                          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


                          • #14
                            Re: Memo fields

                            I can't say for sure since I had done some repairs manually. But I didn't even know about this. I need to read more.

                            Comment

                            Working...
                            X