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

DBF size limits

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

  • #16
    Re: DBF size limits

    That's around 17 million records when i hit the 2GB mark I guess it's good enough for my application for now..CMIIW
    If you believe you may hit that number, may I suggest you make to table of the one and connect them into a 2 table set with a 1 to 1 connection. That could about half the size of each record and you could go from about 17 mil to 34 mil. It is easier to do while the db is young and small than to wait.

    Just a thought.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


    • #17
      Re: DBF size limits

      Originally posted by G Gabriel View Post
      I was going to do that.. the subtraction thing.. when I noticed that alpha tells you at the bottom (in v8, don't know where it would be in other versions) what the record size is. It's all there, so there is no need for any subtractions..
      Funny thing about alpha is i kept finding I did things the hard way... I saw that record size number before but my table was unpacked so I didnt notice why 117 added up to 17,998 for mere 5 records....Do you find what I find here ? If i subtract manually it's 1 + the record size... 118 vs 117 in my case that 1 byte difference means 150,000 records...

      Thanks for the tip GabrielG I dont think my application is going to be on the same scale as yours any time soon... Unless our company is making it in fortune 500 we may not even hit 2 million records in 3 years...

      Originally posted by Tom Cone Jr
      This may be way off base, so disregard if it is not immediatelly helpful.

      The only time I've come close to hitting the DBF limit was when I had a corrupted memo file. You might check the file sizes of all the FPT files in your database. Are any approaching 2,000 megabytes? If so, that's almost certainly a sign that the memo file has become corrupted.

      -- tom
      Thanks for the heads up Tom Cone Jr... No memofields yet...for now...hopefully never LOL....

      Originally posted by Dave M
      If you believe you may hit that number, may I suggest you make to table of the one and connect them into a 2 table set with a 1 to 1 connection. That could about half the size of each record and you could go from about 17 mil to 34 mil. It is easier to do while the db is young and small than to wait.
      Thanks for the heads up DaveM... I'm doing a table that records a fleet of heavy equipments' activities.. I guess I can separate between brands or types like dumptrucks and non dumptrucks like that.. I'll see to do that when the fleet pass 100... right now we only manage 50...

      Comment


      • #18
        Re: DBF size limits

        I guess I can separate between brands or types like dumptrucks and non dumptrucks like that.. I'll see to do that when the fleet pass 100... right now we only manage 50...
        Not really what I meant. I take a table and put in 200 fields and it grows fast. If I split that table into 2 I have 100 fields in each. split it to 4 and i have 50 fields each.

        Explain: I can(in my big app)combine buyer, co-buyer, deal, purchase info in one table. That is about 340 fields. I have seperated it so I have buyer and cobuyer in one(120 fields), deal(120 fields) and purchased(100 fields). These are connectect via a set on a numeric field that is in each table. I do not split different people into different tables. That becomes a hassle.

        Explain2: all your trucks and base info in one table, all other information about trucks in another table connected in a set that uses 1 field to connect the 2 tables 1 to 1. That way the set sees all the information as one record. Make a form(S) on the set and reports can be also made on the set. You can don maintenance/repairs in a 3rd table as a one to many if you need 1 to many.

        Hope this helped.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


        • #19
          Re: DBF size limits

          That makes sense to me... Separate the fields...Reduce record size per table....Thanks

          Comment

          Working...
          X