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

Cannot Append records After DBF Table size Reaches 2 GB

  • Filter
  • Time
  • Show
Clear All
new posts

    Cannot Append records After DBF Table size Reaches 2 GB

    Hi guys,
    This issue took me a pretty long time to figure out, Now, I would like to know if there is a way pass it, without deleteing records.

    I have a table with 64 fields that I append our inventory to twice per day, this is to create a snpshot ot the inventory. This "Products_Snapshot.dbf" now has over 2 million records, the table's file size is 2GB and it refuses to accept any more. records. The error reads . . .

    Error Running Append Operation
    An attempt was made to move the file pointer before the begining of the file.

    After searching the message board I thought it was the memo field that was causing it due to corruption, so i deleted it, which solved the problem for a few days, now its back. Now I realize that it wasnt the fact of deleting a corrupted memo field that made it work again, but because deleting it made the table's file size smaller, but now it has grown back to its 2GB size. As a test, a deleted older records and it took the append operation ok.

    I didnt know I was limited to a 2GB file size limit on NTFS, Or is this a DBF limitation, How can I best get pass this without deleting records?

    Re: Cannot Append records After DBF Table size Reaches 2 GB

    I just found this after some Google searches. It seems DBF does indeed has a 2GB limit, in this case im guessing there is no way around this without jumping to another table.


      Re: Cannot Append records After DBF Table size Reaches 2 GB

      Correct. You likely have your own reasons for having a table for a snapshot of the products. Would make more sense to me to have a table for product inventory and update that twice a day keeping only current values. You could backup that table for reference purposes before each update.
      There can be only one.


        Re: Cannot Append records After DBF Table size Reaches 2 GB


        Check this link for Alpha's database specifications.


          Re: Cannot Append records After DBF Table size Reaches 2 GB

          Nigel, to get around the limit, you can "archive" records. Create a new table with an identical structure to the one that is growing past the 2g limit. Once you have that, you can append the oldest records from the source table into the archive table. Obviously this will have to be done on a regular basis to prevent running into the 2g limit. You can select records for archiving based on criteria that make sense for the data, all the records for a given year, for example. Then you can redirect queries and reports to the archive table if records for that year are needed.

          I'm not sure what would make sense for the inventory table you describe, but if the records go back multiple years wouldn't it make sense to remove the oldest?


            Re: Cannot Append records After DBF Table size Reaches 2 GB

            Thanks guys, At least the puzzle is solved as to why my appends were failing, I still have to figure out which is better now, deleteing or archiving. I have never had to create a form or report that had to figure out which tables to read from before. So, Archiving and still making it easily accessable to the users will give me a challege , but I think Im ok now. Thanks again.


              Re: Cannot Append records After DBF Table size Reaches 2 GB

              May be out of whack with this thought, but a thought:

              can you use a sql solution for this in some way.
              The record limits are vastly larger with sql and might be a thought for archival. You could still access the data as needed with a connection from alpha.
              Dave Mason
              [email protected]
              Skype is dave.mason46


                Re: Cannot Append records After DBF Table size Reaches 2 GB

                Hey Dave, I know I cant hide from it forever, but up until now I still have no experience with SQL, I have never given it a real shot and have not gotten anywhere with it. But, it does makes sense to head that way.


                  Re: Cannot Append records After DBF Table size Reaches 2 GB

                  I just meant to use for archives. You can still connect to the tables from alpha and use for reports and such.
                  I am not a fan of sql on desktop either, but this is bit of a unique situation.
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46