[AccessD] Error 3014 Cannot open any more tables

[Jim Dettman]

 <<File sharing locks 
have nothing to do with the recordsets in a FE however.  Those locks 
control access to the BE.>>

 Of course they do.   The file locks are held by the OS where the database
containing the table resides, but that's done are the request of the
client/FE working with the recordset.   If the db engine can't take out any
more locks, a error is raised.

 Typically though, that's "Not enough resources".   This error is usually
bumping into the 2048 table ID limit.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
John Colby
Sent: Wednesday, April 26, 2017 04:24 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error 3014 Cannot open any more tables

It turns out that any form and any object like a list or combo on the 
form also opens a recordset.  Thus this exact problem can be caused by 
overly complex forms.  However she expressly says it is a single 
"simple" form so that is probably not the issue.  File sharing locks 
have nothing to do with the recordsets in a FE however.  Those locks 
control access to the BE.

On 4/25/2017 6:55 PM, Rocky Smolin wrote:
> Is there a registry key that can be increased like the MaxLocksPerFile
hack:
>
>
https://support.microsoft.com/en-us/help/815281/-file-sharing-lock-count-exc
> eeded-error-message-during-large-transaction-processing
>
> http://tinyurl.com/l77zk7f
>
> to allow more tables?  Although John's probably right - you probably don't
> need that many tables open.
>
> Can you trap that error and run a few lines of code which would list all
the
> open tables? Maybe you could spot the culprit?
>
> R
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Janet Erbach
> Sent: Tuesday, April 25, 2017 2:39 PM
> To: Database Advisors
> Subject: [AccessD] Error 3014 Cannot open any more tables
>
> Hello, all.
>
> I deployed a 2007 app today that is supposed to be up and running all the
> time.  It's relatively simple - one form bound to a temporary table that
is
> emptied and refilled every minute on the form timer event.
>
> After about 30 minutes, the app throws a 3014 Error - cannot open any more
> tables.
>
> We are running jet 4.0, which is the most current, yes?  If this is truly
a
> jet related error, there are a couple of things I can do to help optimize
> the app - about half the queries in the app are run from saved query defs,
> and I can convert all those to sql statements.  I've decompiled and
> reinstalled the access database engine, both suggestions that turned up in
a
> google search.  But beyond these troubleshooting steps, I don't know what
> else to do.
>
> Can you please give me some clues on what may be triggering this?  I
haven't
> seen this error before (that I can remember, anyway) and I have another
app
> deployed on the shop floor which runs 24/7 and refreshes every minute
> without any issues.  Any help is greatly appreciated!
>
> Janet Erbach
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

-- 
John W. Colby

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