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

Error: "Out of Memory" When Adding New Fields To Table

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

    #16
    Re: Error: "Out of Memory" When Adding New Fields To Table

    Originally posted by Al Buchholz View Post
    Robin

    That works. Have you had trouble with that process?
    Only when the table had records already. Like Dave said, field rules and order entry are two problems that could crop up. It just seems like good practice to add the new fields to the end - no?
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #17
      Re: Error: "Out of Memory" When Adding New Fields To Table

      At the end is the way to go Robin.
      Dave Mason
      [email protected]
      Skype is dave.mason46

      Comment


        #18
        Re: Error: "Out of Memory" When Adding New Fields To Table

        I used to have issues with re-ordering fields in version 4.5, and prior. Are you guys sure that problem still exists?

        Since around that time, I always jockey fields into a logical order.

        I move the field around as frequently as needed for one simple reason. I group them by association to each other.

        For me, this works well across the spectrum of reasons that it would.

        1) When re-visiting tables I have not been in for months or years, I am more likely to 'Remember' what each field is there for.

        2) As I use the traditional field rule editor more than the newer means available, setting up field rules is easier as the fields are grouped (At least in my head).

        3) Fields continue to be grouped in Excel exports, when making forms and reports in the dragdrop list, etc.

        Anyway, no problems for me that I can remember in recent years. Maybe I am just lucky??? That would be a first...

        Comment


          #19
          Re: Error: "Out of Memory" When Adding New Fields To Table

          Originally posted by MoGrace View Post
          Only when the table had records already. Like Dave said, field rules and order entry are two problems that could crop up. It just seems like good practice to add the new fields to the end - no?
          I have seen long index names truncated by adding fields regardless if added at the end or not, which would cause other issues including field rules and run on sentences.....

          But overall no difference if fields are added at the end or somewhere else.

          As always, verify that the table and structure is what is intended after the procedure.
          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


            #20
            Re: Error: "Out of Memory" When Adding New Fields To Table

            I used to have issues with re-ordering fields in version 4.5, and prior. Are you guys sure that problem still exists?
            I have seen issues with this in v7 which I used for a very long time.
            In testing with v11, I saw no issues, but have no reason to use it. I did not use v8,v9,v10 very much.
            working hard in v12 these days and still have no reason for ordering.
            May test it again some day.
            One thought is, my tables are usually smaller than some at 3 to 140 fields at most and the 140 is a real oddity.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


              #21
              Re: Error: "Out of Memory" When Adding New Fields To Table

              I duplicated the table with only field rules being copied, After that I was able to add the new fields to the new table. But I wasn't able to append the records from the original table to the new table because the original table does not show in the Operation genie.


              Here's what I discovered when I checked the file size in windows explorer.
              products.DBF = 2.56 MB
              products.FPT = 1.38 GB
              products.DDM = 402 KB

              So, I guess the verdict is in, corrupt Memo field. The most promising solution I've found so far is: this one by Tim Sutherland

              "We have tried all the memo repair utilities and have never had any success. Our table has around 300,000 records in it and the only way we can repair it is to delete 50 percent of the records (on a backup copy), compact the workspace, check the FPT file size, repeat... We keep doing this until we can isolate the record. Once the record is isolated, we delete it, re-enter it and get back to normal. This is often a several hour, not to mention tedious, process."

              Is this really the best solution?
              Last edited by nigeldude; 03-22-2015, 09:03 PM.

              Comment


                #22
                Re: Error: "Out of Memory" When Adding New Fields To Table

                yes. I think it was originally proposed by Tom Cone, but does not matter.

                Many times just appending the records will take care of it, but you said that is not happening? I have had to type the table name in to get it to work for append.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment


                  #23
                  Re: Error: "Out of Memory" When Adding New Fields To Table

                  Yes, and to avoid the issue in the future the usual suggestion is to have the memo field in its own table with a single field that links to the main table. A set is created with the main table as the parent and the memo field as a child. If that is not viable in your situation then consider http://www.learn alpha.com/MemosThat...osThatWork.htm

                  Dave is correct. After a certain point(number?) all the tables in the database no longer show in the smart field selector in the genie. You can then type the table name or use the first option at the top of the table selector <More Files...> and navigate to the table.
                  Last edited by Stan Mathews; 03-22-2015, 10:28 PM.
                  There can be only one.

                  Comment


                    #24
                    Re: Error: &quot;Out of Memory&quot; When Adding New Fields To Table

                    Originally posted by nigeldude View Post
                    So, I guess the verdict is in, corrupt Memo field. The most promising solution I've found so far is: this one by Tim Sutherland
                    No I'd guess that you have data in a field that is bad.

                    If the memo field is corrupt, usually the size of the memo file is a little over 2 gb.

                    Duplicate the table and chose all the options including the records and see what happens.

                    or

                    Do you have a backup copy with a much smaller FPT? Use that and rebuild from there.
                    Last edited by Al Buchholz; 03-22-2015, 11:07 PM.
                    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


                      #25
                      Re: Error: &quot;Out of Memory&quot; When Adding New Fields To Table

                      Originally posted by nigeldude View Post
                      Is this really the best solution?
                      No.
                      There is a function to fix "bloated" memo fields. I recommended in the past several times, but for the life of me, I can't remember it right now and can't search for it that easily as I am not that good with alphapedia. I am used to the old help file. Maybe someone else can point it out.

                      Comment


                        #26
                        Re: Error: &quot;Out of Memory&quot; When Adding New Fields To Table

                        Here is one, but I think there is another:
                        <TBL>.MEMO_CHECK()

                        Comment

                        Working...
                        X