table capacity

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rahmansaputra
    New Member
    • Nov 2015
    • 6

    table capacity

    Dear all,
    How limits the size of the capacity of a table in ms access if a table contains thousands of data and each data contains the attachment.
    if there is no limit how many gigabytes?
    and what can we setting to enlarge its capacity
    How to do,

    Thank you

    Ira
  • hvsummer
    New Member
    • Aug 2015
    • 215

    #2
    Access has 2 GB limit, so you can only have 2 GB database, around 3 or 4 million rows records.

    Comment

    • zmbd
      Recognized Expert Moderator Expert
      • Mar 2012
      • 5501

      #3
      32Bit Install - 2GB
      64Bit Install - (not recommended read here) are given as the limit of your PC's memory specifications.

      These are the general specifications for ACC2010-32-Bit installation. These have not significantly changed in ACC2013-32-Bit installation:
      Find limits and specifications for Access 2016 database files and objects, such as the maximum file size or the maximum number of fields in a table.


      + to add to this, images and attached files will quickly consume the 2GB limit for 32-Bit Office installations; however, images at 5Mp convential wisdom places that at around 500 to 600 images depending on the format and the system-objects in the database so your actual limit may vary significantly. So, off-hand, a single table of records with attachments would have general upper end of 500 records depending on the attachment size and type along with the database design.

      Many of the experts here will usually recommended not to use the "attachment " field to store the image in the database, instead, storing a link to the file location ( see one example here ). However, I've a few cases where this type if storage is needed and to work around the 2GB limit I have multiple back-ends.

      You really have no options to increase the Access size limit in and of itself there are, however, workarounds:
      +To maximize the number of storable records, design your database as a split, front-end/back-end, format from the start. This will give the almost the full 2GB in the backend for data storage.

      Again, I have used this method to store images that for various reasons had to be protected wherein I have a front-end, a data-only-backend, and an image_document-only-backend(s). The data-only-backend has 1000's of records; however, I have several image_document-only-backends. Again, I would advise against this method for most applications.

      + Upsize your backend files to a full database sever such as MySQL, MariaDB, Oracle, SQL-Server, etc...

      + to use a 64-Bit Office installation on a 64-Bit OS; however, as most Office installs are 32-Bit you will find compatibility issues when attempting to use the database between these versions (see the link at the top if this post for MS's discussion of these issues).
      Last edited by zmbd; Nov 23 '15, 06:10 PM.

      Comment

      Working...