Will MS-Access exceed 2 GB limit in a future version ? / wish list

  • Thread starter Thread starter Michael Reb
  • Start date Start date
M

Michael Reb

Hi,

will MS-Access exceed the 2 GB limit per Database some day ?

There are standalone/single user applications which are working well but are
based on huge data volumina. They don´t need server functionality for
multiple internet access or improved data recovery etc.
It is possible to build high performant databases in Access using JET/DAO as
long as one doesn´t need multi user access. I got such a database
application containing about 2 GB and meeting user requirements regarding
response times.
The 2 GB limit is in effect since the first versions of MS-Access, though
Hardware and Software became quite faster meanwhile.

Perhaps there is somebody out there who can answer or even promote ;-) this
request.
I once wrote that to MS support but didn´t get an answer then.

Does anyone know the correct place to post MS-Access wishes ?
Since versions I hoped to get bigger dialog boxes , e.g. for selecting
tables/queries in Query design view.

Michael
 
I think it's very unlikely that that limit will be increased.

You can always link your front-end to multiple backends, thereby expanding
the size to (theoretically) the size of your hard drive.

One of the regulars reports a multiuser Access 2.0 database (which had a 1
GB limit) linked to in the range of 23 GB worth of MDBs.
 
Douglas J. Steele said:
I think it's very unlikely that that limit will be increased.

You can always link your front-end to multiple backends, thereby expanding
the size to (theoretically) the size of your hard drive.

One of the regulars reports a multiuser Access 2.0 database (which had a 1
GB limit) linked to in the range of 23 GB worth of MDBs.

Actually, it was over 30GB, had 89 tables, each connected from a separate
database. To my knowledge, it is still running, but I haven't seen this
customer in about 2 years now.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
But with multiple Backends you cannot use application-wide referential
integrity (cross the diverse backends) without coding trigger-like
application logic.
In case of tables being bigger than 2 GB coding becomes even harder when
those tables have to be divided within themselves.

Michael
 
Simply amazing Arvin...

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #15 of 19: 5 dialogues = 1 decalogue
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
You are correct that you cannot define relationships and enforce referential
integrity at the engine level between multiple databases. As far as I know,
the only way to handle tables nearing 2GB that require RI is to pungle up
for a server database such as full Microsoft SQL Server. Access is a great
tool for creating client applications to SQL Server.

And, all in all, it's suprisingly robust (BUZZWORD ALERT) for something that
people thought was just another little desktop database back when it was
released.

Larry Linson
Microsoft Access MVP
 
Arvin Meyer said:
Actually, it was over 30GB, had 89 tables, each connected from a separate
database.

Ah, that's right. It contained one row for each piece of sushi you've
consumed if I recall correctly.
 
LOL

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #15 of 19: 5 dialogues = 1 decalogue
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
Back
Top