Make 32-bit Access large address aware (LAA)
Now that the 32-bit version of Outlook 2016 becomes large address aware (see https://support.office.com/en-us/article/Large-Address-Aware-in-Outlook-2016-ea0913e4-2917-4456-b0ea-935dbd57ef02), it would be great to get that for MS Access as well.
(We hit the 2GB barrier every now and then when batch-exporting MS Access reports as PDF. Having 4GB support would be great. Upgrading to Office 64-bit is usually not an option in corporate environments depending on third-party add-ins.)
Anonymous
shared this idea
Thank you for your feedback. This work is in scope to be completed within the next few months. The Access team appreciates your patience in advance.
29 comments
-
Hansruedi
commented
+1 thank you
-
Anonymous
commented
Yes Please add it.
-
Anonymous
commented
Yes, please add it ASAP to Access.
-
Admin, 3D-plastic
commented
Just patch Access with /LARGEADDRESSAWARE...
(see https://www.insidesql.org/blogs/2019/12/20/minimize-access-32-bit-memory-problems-on-64) -
Klaus Neidl
commented
Do it ASAP!
-
Andreas Heiderstaedt
commented
Yes Please add it.
-
Dieter Staudenmaier
commented
I agree to the other posts - please change the barrier
-
Anonymous
commented
I agree with Stephan, he wrote:
Some complex MS Access Applications don´t run with Access 2019, because there is not enough free virtual memory.
The only way is to transform the 32 bit version into 64 bit.
A lot of work for nothing.
-
Anonymous
commented
We wait for the LAA
-
Anonymous
commented
Yes, please add it
-
Adrian Bell (MVP)
commented
@Stefan.
Please understand that comments for or against an idea in here are appropriate.
Diluting, or otherwise trying to adjust the original request that people have been voting for and commenting on is not so much. It would make managing of requests impossible.As for making such a change to older versions that you suggest, I believe this is outside of the scope of their management in that changes to older versions are restricted to security changes only.
If you believe, in spite of what I say, that this should be considered then what you must do is to post it as a suggestion in its own right. Adding it in here can only distract.
-
Stefan Wurmb
commented
Please also add this flag to the older 2010/2013 Versions too. They are still being used.
-
Peter Fors
commented
Will this solve the issue "Cannot open more databases"?
-
Josef Schasching
commented
PLEASE change this, I have very often this problem
-
Anonymous
commented
https://accessusergroups.org/et/event/access-et-2-2019-12-20/ (Video by Karl Donaubauer + Files)
https://www.insidesql.org/blogs/2019/12/20/minimize-access-32-bit-memory-problems-on-64 (First half is german, second the english translation) -
Bob Alston
commented
Yes Please add it.
-
Thomas Becker
commented
I first heard about it on DonKarl.com I had extreme trouble in the past due to the memory problem in my applications.
If I now hear that Excel and Outlook have had this for a long time, I can't understand it anymore.
Please listen to the developers!!! It is urgently necessary that this is implemented in the standard! -
Ben Sacheri
commented
Here's a video by Karl Donaubauer where he demonstrates the issue and shows ways to work around this problem. Our plea is for Microsoft to make this feature built-in to Access so no hack is needed.
-
Brian
commented
Long overdue. Such an easy fix for otherwise extremely complex workarounds.
Agree "This has to be done!!!"
-
Adrian Bell (MVP)
commented
What can I say that hasn't been said already?
I can't say how hard a change it might be to make, but as far as benefits go it seems a no-brainer. Access is an environment where many many applications have been around for years and often they've grown far beyond original designs. This frequently leads to problems with this 'artificial' 2GB limit. Doubling that would add years to the viability of some projects.
Thos would really make a difference.