[AccessD] Fwd: Re: Ac2013 running out of resources

[James Button]

As a slight aside from the detailed and discussed problem 

I believe there are options specifiable at windows startup to set windows to
allow 32 bit applications to use 3Gb of memory rather than just 2GB,,
Additionally, for 32 bit OS the amount of real memory available includes the
memory allocated to the video system
So having a video board with 1GB of onboard memory may well reduce the memory
allocation available to many of the applications by that 1GB
Or even more memory than is on the video board if the board adds main memory to
the allocation it acquires (reserves) from the OS's managed space.

JimB



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ryan W
Sent: Wednesday, January 25, 2017 6:17 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Fwd: Re: Ac2013 running out of resources

For the record I put Access 2016 Runtime on a VM and got "about" the same
experience. Using the VMMap.exe tool it seemed I was able to utilize about
1.6GB of virtual memory for MSAccess before I ran into resource errors.
With 2013 it seems to happen around 1.45-1.5GB.

On Tue, Jan 24, 2017 at 6:11 PM, John Colby <jwcolby at gmail.com> wrote:

> And did they fix it in 2016 or whatever the current version is?  Or is
> this just another "develop in vba at your own risk" message from MSFT?
>
> On 1/23/2017 8:46 PM, Bill Benson wrote:
>
>> Ryan this is FYI
>>
>> >From my non-flammable Note 3,
>> Bill Benson
>> ---------- Forwarded message ----------
>> From: "Mark Simms" <marksimms at verizon.net>
>> Date: Jun 8, 2015 9:43 PM
>> Subject: Re: [AccessD] Ac2013 running out of resources
>> To: "Access Developers discussion and problem solving" <
>> accessd at databaseadvisors.com>
>> Cc:
>>
>> Thanks Jurgen - this totally confirms my suspicions: BUG
>>
>> How much memory can AC-2013 consume ? Try 65 GIGs.
>> Yep...I've seen it in Task Manager. Unbelievable.
>>
>> Another QA debacle by MSFT.
>> Attempt development with AC2013 AT YOUR OWN RISK.
>>
>>
>>
>>
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http:// <http://www.databaseadvisors.com>
>> www.databaseadvisors.com
>>
>
> --
> John W. Colby
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com