[AccessD] System Resources Exceeded

John Colby jwcolby at gmail.com
Wed May 8 18:45:46 CDT 2019


Could also be too many "recordset" objects open.

On Wed, May 8, 2019, 9:52 AM RANDALL R ANTHONY via AccessD <
accessd at databaseadvisors.com> wrote:

> Hello Group,
> Just had a weird error pop-up on a relatively stable, small DB.  Win7 and
> Win10 OSs, some with Access13, some with Access16 FE and BE.  Happened once
> about two months ago, did a C&R and the problem went away.  However the
> customer is reporting the issue is now occurring about 50% of the time.
>
> Simple import routine, loads .txt file data (10 to 100 records) to a temp
> table, then loads them to staging table and from there does a randomizer
> routine to load to a table assigning X amount of records to any particular
> auditor.  This process takes maybe a minute?  Two minutes?  Part of that
> latency is due to extreme network distance from the user and the server
> farm, however that's never been an issue.
>
> Googling this the only suggested answer to the issue was provided by a
> Mark-NC, see below.
> I have seen this problem when running Access on a computer with multiple
> processors. Try changing the Processor Affinity for the MSACCESS process in
> Task Manager down to just one processor, and see if that improves
> performance.
>
> Any help/clarification on this is greatly appreciated.  Thanks.
>
>
> Randy Anthony, MCP
> Database Administrator
> 4456 Corporation Lane, Ste. 200
> Virgina Beach, VA 23462
> 757-252-8107
>
> .
> --
> 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