[AccessD] 64-but ONLY front end ?

[Ryan W]

Those stats are for a function I am running within access. Not via ProcMon
or other.

Function ReturnVM() As Double

    Dim Mem As MEMORYSTATUS
    Dim Result As Integer

    Mem.dwLength = Len(Mem)
    GlobalMemoryStatus Mem

    ReturnVM = Format((Mem.dwTotalVirtual - Mem.dwAvailVirtual) /
1073741824, "0.000")

    Debug.Print ReturnVM & " GB of VM used."

End Function

On Fri, Jan 6, 2017 at 8:40 AM, James Button <jamesbutton at blueyonder.co.uk>
wrote:

> Re stats -
> Seems to me that you are not looking at all the available columns under the
> details tab
> Use View, or right-click on the column headers - and add all -
> Then narrow the entries that do not concern you -
>
> The message (from memory) means that some of the supporting table and
> controls
> areas have exceeded the limit they are allowed.
> (I'm guessing here - as I'd need the tech reference etc., but consider if
> every
> one of the tabs and scripts in all the 'stuff' needs to have link and usage
> entries in a 64MB area of memory)
>
> That would mean that the actual amount of virtual, or even real memory is
> irrelevant - and going 64 bit means double the space within that 64MB are
> is
> used for each memory link, or counter etc.
>
>
> If you are storing data, then that would ( I expect) go within the main
> pageable
> area, along with the not-currently-actively-in-use forms, but the links to
> them
> - private unpageable memory allocation ? would need to have pointers to
> their
> localtion in 'memory'
>
> Hope the above helps you get at what actions are exceeding the within
> Access
> limits
>
> JimB
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Ryan W
> Sent: Friday, January 6, 2017 2:28 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] 64-but ONLY front end ?
>
> More statistics:
>
> ?returnvm
>
>
> (Reporting module loaded)
> 1.391 GB of VM used.
>
> (Prepatory form loaded)
> 1.194 GB of VM used.
>
> (Analytics form loaded)
> 1.135 GB of VM used.
>
> (Login Form loaded)
> 1.06 GB of VM used.
>
> (Switchboard Loaded)
> 0.803 GB of VM used.
>
> (Nothing open but my Access FE (no forms loaded))
> 0.645 GB of VM used.
>
>
>
> With that once I get to the reporting module if I hit "print preview" on
> all of my selected reports (7) to print and give to the client I get an out
> of resources error.  Those are the most used forms in the entire FE.  It
> wouldn't be uncommon for some of our data reviewers to have all of those
> open bouncing between them (they used to do it before via hotkeys (Ctrl-R
> for Analytical, Ctrl-M for Main, Ctrl-B for Prep, Ctrl-W for Login etc)..
> so even though you PREVIOUSLY with Access 2003 you couldn't see a tab, the
> same forms were loaded then that are loaded now. The key difference is
> Access 2013. It must simply use more memory.
> --
> 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
>