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

Out Of Memory Error on Restructure Table

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

    Out Of Memory Error on Restructure Table

    I'm using Alpha 5 v4.03 on a PIII 733 with 320MB of RAM. When I attempt to remove a field of a table, the progress window reports 70 records of about 17,000 processed, then the system pauses, the hard disk chugs, and then I get an "out of memory" error.

    I have scoured this message board for a related problem, but I don't see anything related.

    I am in the middle of upgrading my DOS-based Alpha 4v3 order entry/invoicing routines to Alpha 5.

    Any suggestions?

    Thanks!

    Jon Schwarz

    #2
    RE: Out Of Memory Error on Restructure Table

    Jon,

    It sounds like Alpha is looking for something it can't find, perhaps on the 71st record. Beyond that, I can't answer your problem directly, but I have found the best approach to transferring from A4 to A5 is to first create a new table structure in A5 and then append the a4 data. In this way, any corrupted data will be found during the append. I also copy the A4 tables (databases) to a new location before append to leave the originals untouched. I don't particularly like doing basic design on live data. I add test data to try out ideas and then later transfer all data for more testing. Maybe try working with the table with only a few records first. There are a couple older posts about how to append small amounts of data to test for corrupted files.

    Jerry

    Comment


      #3
      RE: Out Of Memory Error on Restructure Table

      It sounds you have a corrupted memo file check the size of the FPT file in windows explore

      Daniel Weiss
      Daniel Weiss
      EZ Link Software

      Comment


        #4
        RE: Out Of Memory Error on Restructure Table

        Hi, Jerry!

        This IS my test data. The live stuff is still being entered on the DOS system (as it slowly dies). :)

        Maybe I should restructure the database in Alpha 4 BEFORE bringing it over.

        Otherwise, I followed the steps you mentioned. Will emptying the set and re-appending the databases work?

        I have my data entry layout all set up and it would be a shame to trash it and start from scratch.

        Thanks!

        Jon

        Comment


          #5
          RE: Out Of Memory Error on Restructure Table

          Hi Daniel!

          The size of the related .fpt file is 1KB. I only brought the .dbf files over from the old system. Was that a mistake?

          Comment


            #6
            RE: Out Of Memory Error on Restructure Table

            what do you mean by "I only brought the .dbf files over from the old system"?
            Daniel Weiss
            EZ Link Software

            Comment


              #7
              RE: Out Of Memory Error on Restructure Table

              I mean that I did not bring the support files over (the field rules, the layouts, the indexes, etc.) because they were not selectable from Alpha 5 on my new system. It seemed to me that Alpha 5 creates and uses a totally different support file scheme than Alpha 4.

              Am I missing something?

              Jon

              Comment


                #8
                RE: Out Of Memory Error on Restructure Table

                I�m really not familiar with this issue at all I never tried converting from A4. Sorry
                Daniel
                Daniel Weiss
                EZ Link Software

                Comment


                  #9
                  RE: Out Of Memory Error on Restructure Table

                  A5 takes the A4 memo fields and converts them (if I remember correctly) from .dbt to .fpt extension. So to open an A4 table in A5 copy filename.dbf and filename.dbt to the new location.

                  Bill
                  Bill Hanigsberg

                  Comment


                    #10
                    RE: Out Of Memory Error on Restructure Table

                    Hello Jonathan,

                    You've got some corruption somewhere. Alpha is stepping through the records and hits something that causes it to 'gulp'. Right click on the table and choose the Pack table choice from the pop up menu. See if a pack will run through the entire table. My guess is it will stop at the same place. It could be a memo field problem, an index problem or some corrupt data or data type problem in the table itself. You are getting to the 70th record so the problem is probably in that area. There are several techniques to solve this problem, first and easiest is to run a pack and or database compact, and or an index update routine (database compact does it all for all tables and sets, pack does a single table pack and index update, and index update does just that for a single table). You can create a duplicate table and copy the records over. In difficult but less than killer problems like this, I've found that creating a duplicate but EMPTY table and then copying the records with a simple xbasic script will many time solve these problems. You can do the same thing with alpha's built in append routine, but I feel I've had better luck with a simple xbasic routine to copy the records.

                    Good luck,
                    Jim

                    Comment


                      #11
                      RE: Out Of Memory Error on Restructure Table

                      Hi Jim!

                      Thanks for the advice. I already packed the database; the operation ran flawlessly; the problem persists. I'll try the solution with an empty table next.

                      Jon

                      Comment


                        #12
                        RE: Out Of Memory Error on Restructure Table

                        Jon,

                        Another area to explore. Do you have any scripts on events for the new table or it's forms? How about any field rules that refer to the field being removed? If a script is running and has an error, it may not clear out of memory, especially if the script is referencing the field that is being removed. After a number of records, you could get an out of memory error.

                        Jerry

                        Comment


                          #13
                          RE: Out Of Memory Error on Restructure Table

                          No scripts are running. However, there is a form that references some fields that I am trying to remove. I was under the impression that the field rules that referred to the fields I am removing would be deleted along with the fields.

                          Jon

                          Comment


                            #14
                            RE: Out Of Memory Error on Restructure Table

                            Like the old saying, never assume anything. I don't want to guess how many times that has gotten me into trouble. I would try to remove any references to the field before I remove it, including fields on forms. The fact a field is referenced in a form should not matter, except when you open the form.

                            Another little thing I ran into a long time ago was odd behavior when the field being removed was in the middle of the table structure. I even forget what the problem was, but now I always move the field to delete to the last field in the structure, save the structure and close, reopen structure and then delete the field. This seems to work fine every time.

                            Jerry

                            Comment


                              #15
                              RE: Out Of Memory Error on Restructure Table

                              Thanks, Jerry!

                              I'll try out your suggestion. I haven't had any time in front of Alpha 5 today, but I'll try it out as soon as I sit down to work on it.

                              Jon

                              Comment

                              Working...
                              X