How many records does Access hold?

[Tim Loeffelholz]

I'm curious as to how many records Access is capable of
holding. Is there any record count difference from Access
2000 to Access 2003?

 

[Douglas J. Steele]

There isn't a limit in terms of number of records, just in terms of the
entire file size. An MDB file cannot exceed 2 GB for Access 2000, 2002 and
2003. However, since you can link to other databases from within an MDB,
essentially you can go as large as you want.

 

[Crispy]

How can I link to other databases?

I have the 2GB problem and would love to be able resolve that issie so I can
continue to add files...!

Is it also possible to export out data to another database so I would not
have to re-enter data for over 1500 records?

Thanks

 

[Immanuel Sibero]

Hi Crispy

Have you compacted the database?

The process of linking to another database is usually a part of the common
practice of "splitting the database" that is dicussed a lot in this
newsgroup. You would split your .mdb file into two .mdb's. One contains the
data only i.e. tables. This mdb is commonly referred to as the Back End. The
other contains everything else i.e. forms, queries, reports, vba modules
etc. This mdb is commonly referred to as the Front End.

This split design gets around 2GB file size limitation on an .mdb file. If
your application requires or, in a short time, will require more than 2GB
even after compaction, you may have to design your application where you
implement multiple backends. If I was in this situation, I would seriously
consider more robust backend, something like SQL Server.

I encourage you to find more information on "splitting the database" in this
newsgroup.


HTH
Immanuel Sibero

 

[John Vinson]

How can I link to other databases?

I have the 2GB problem and would love to be able resolve that issie so I can
continue to add files...!

Is it also possible to export out data to another database so I would not
have to re-enter data for over 1500 records?

If you're pushing 2 GByte with only 1500 records, I have to assume
that you're storing images in your table: Access is notoriously
inefficient at doing so. Even if you have compact .jpg images, Access
will bloat - it stores the .jpg bits, *AND* creates a bitmap image and
stores it (much bigger), *AND* stores massive system overhead
information.

The usual solution is to store the images externally. See the links at

http://www.mvps.org/access/forms/frm0030.htm

 

[Guest]

I am also curious of this question. Is there anyone out there that knows?

 

[Guest]

Sorry, saw responses after I learned how to scroll.