[AccessD] Ac2013 running out of resources

[Jim Dettman]

<<BTW:I like that setOption MaxLocks idea.....I'm going to try that.>>

 If you have Insert, Update, Delete's, you can also set the queries
UseTransaction property to no.

 With that set to no, once JET hits the lock limit, it commits even if it's
still executing the query.  You can never run out of locks this way.

 If it's set to yes, then JET will maintain a lock on every record it
touches until the query is complete.

 The default lock limit is only like 9,500

Jim.


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Mark Simms
Sent: Sunday, June 07, 2015 02:01 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Ac2013 running out of resources

Interestingly gang- there was a hot fix for this resource problem for
AC-2010.


Would it be possible the AC-2013 dev team never incorporated this fix ?

BTW:I like that setOption MaxLocks idea.....I'm going to try that.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com