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

Bill Benson bensonforums at gmail.com
Wed Jan 25 15:19:48 CST 2017


The you will just have to pay attention to at what point in the process you
spike above 1.2 or 1.4 gb and go from there.

On Wed, Jan 25, 2017 at 2:01 PM, Ryan W <wrwehler at gmail.com> wrote:

> 800MB would crush me. By the time we have the switchboard open we're
> already using 720MB.
>
> Access alone with no MDB/ACCDB loaded is already eating 516MB.
>
>
>
>
> On Wed, Jan 25, 2017 at 12:55 PM, Bill Benson <bensonforums at gmail.com>
> wrote:
>
> > Ryan, 1.4 is about the correct number but I have found a single reference
> > can make it spike so I use >800mb as the cutoff point to warn the user to
> > park and restart the accdb. I have yet to test Dan's suggestion, which I
> > probably won't get to for awhile. Personally I don't think it will help
> > because you and I both get these spikes (unreleased memory) and you are
> not
> > assigning to report variables. For all I know leaving those not set to
> > nothing might or might not have an impact but creating rst's  and looping
> > same is what caused memory to pile up for me.
> >
> > From my non-flammable Note 3,
> > Bill Benson
> >
> > On Jan 25, 2017 1:18 PM, "Ryan W" <wrwehler at gmail.com> wrote:
> >
> > > 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
> > >
> > --
> > 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
>


More information about the AccessD mailing list