Database size limitation - advanced question

[Eric Stevenson]

Does anyone know if there is a way to work around the 2GB
database size limitation on Access mdb's? I have a file
that starts just over 2GB and I was able to trim it back
to 750MB. That file needs to be paired with data that
will likely result in appx a 6-8gb file. I have the
hardware to run this but Access gives me an "Invalid
argument" error. Is there a setting somewhere that I can
use to up the limit???

 

[Douglas J. Steele]

There is no way around the limit. It's a hard limit dictated by the
architecture of Jet.

Is it possible to split your data into smaller chunks, and store each chunk
in a different MDB? From a single front-end, you can link to as many
back-ends as you like.

 

[Albert D. Kallal]

That sounds like a large file...

What is the size after you do a compact and repair?

Are you storing graphics inside of the database...as this often does not
work well at alll...

 

[Eric Stevenson]

Yeah...its a huge file. That is the "compacted and
repaired" size. I am likely going to have to break the db
into 7 parts and link them through 1 interface. Only
issue is that I really wanted it to run in one solid db
and I don't know how to use SQL server

 

[Guest]

Thanks...

I was afraid that was going to be the answer. Looks like 7
db's it is...

 

[Albert D. Kallal]

Hum..as mentioned...is this large tables? How many recodes?

As mentioned, you DO NOT want to store pictures..unless you change the way
you transfer the data to a ole field.

If those files are just large numbers of reocrds..then yes..you are
certainly pushing the limits of ms-access...