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



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

File offset is to (sic) large

  • Filter
  • Time
  • Show
Clear All
new posts

  • File offset is to (sic) large

    I have a table with 60214 records and is 21,313,402 bytes. I have an operation that has worked flawlessly for literally years that appends transaction table records to the larger table. I am now getting an error that states "File offset is to large". NOTE: this is a direct quote not a misspelling. Have I hit the maximum table size? I searched the forum have not found any reference to that error message.
    Attached Files

  • #2
    Re: File offset is to (sic) large

    This is not remotely close to the table size limit, unless you have exceeded the number of allowed fields which is(from my faulty memory) 512.

    Are there memo fields in the tables? if yes, I would suspect memo field corruption.


    • #3
      Re: File offset is to (sic) large

      Thank you for the reply.

      Yes, there are memo fields involved.

      On the supposition that it's a corrupt memo field, I replaced the "faulty" table with one from a back up and tried to run the append again. Now I get an error that states "Error running append operation. Corrupt arena."

      I searched the phorum for "corrupt arena" but didn't find anything useful.


      • #4
        Re: File offset is to (sic) large

        Did you replace ALL of the associated files? .dbf, .ddd, .ddm, .ddx, .ftp? Otherwise, things won't sync up properly.


        • #5
          Re: File offset is to (sic) large


          Yes, I copied all the associated files.

          This is fixed. I presume Finian was correct and it was a corrupt memo field. I went back and restored the table and associated files from 8 weeks ago and then re-appended all the data since then (Yay! that was fun!) but it's operational now.


          • #6
            Re: File offset is to (sic) large

            Bob, there used to be a repair feature for Memo fields.
            They are a real problem sometimes when corrupt and finding the bad one is a pita.
            It might pay to backup the table with the memo fields in it - say daily in a cycle which suits your data usage - so you can back track and restore as soon as you hit a glitch.
            Ted Giles
            Example Consulting - UK

            See our site for Alpha Support, Conversion and Upgrade.


            • #7
              Re: File offset is to (sic) large


              I understand. I actually back up all files every night because Jesus Saves. This is exactly what saved my bacon this time.



              • #8
                Re: File offset is to (sic) large

                I once had a bad memo offset pointers cause an FTP file to grow in size AFTER packing.

                I was able to repair the file by removing the corrupt indexes from the DBF and letting the table.pack() function do the rest. I did loose the memos after the packing but from visual inspection of the FPT data I could see the memo was already lost. Sadly I don't think I had a backup that went back far enough to recover the data.

                FPT and DBF file structures are pretty straight forward and available online. If you don't mind using a hex editor and you might be able to do something similar. You can check my post on the topic, though I fear the solution post I made gets a bit confusing. I think my brain was scrambled after fixing my problem. Like a bozo, I had actually reversed engineered the pertinent parts of the DBF and FPT file structures... before realizing i could just look it up online. *SMH*