[AccessD] Error 3014 Cannot open any more tables

[Darryl Collins]

I will also add,  - Great that you posted your experience, outcome and thoughts back to the list.   That is valuable and helpful for everyone.  Thanks.

Cheers
Darryl.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: Wednesday, 10 May 2017 6:58 AM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Error 3014 Cannot open any more tables

Update on my 'Cannot open any more tables':  my original form had a local temporary table as the data source;  I was emptying it and re-filling it with current data from the network every 30 seconds.  I restructured my code so that it linked instead to the network data directly instead.  (I was using the local table to keep multiple users in this area from printing up copies of the same work order;  I devised a different method to keep that from happening.)

I have not hit error 3014 since.  It was the continual emptying/refilling of the local table that triggered it.  Thank you all for your help.

Janet

On Sat, Apr 29, 2017 at 3:13 AM, Bill Benson <bensonforums at gmail.com> wrote:

> The fact that you are doing something on a timer sounds to me that 
> this is acting like a loop. Do you need the timer to occur as frequently as it is?
> If you changed it to a larger timer interval does the runtime duration 
> improve? If you shrink the interval does it deteriorate? That would be 
> your clue.
>
> From my non-flammable Note 3,
> Bill Benson
>
> On Apr 25, 2017 5:40 PM, "Janet Erbach" <jerbach.db at gmail.com> wrote:
>
> 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
> --
> 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