[AccessD] System resource exceeded. Error No 3035

Jim Dettman jimdettman at verizon.net
Tue Jan 13 05:51:43 CST 2015


 That's why I wrote in the article that apps are "snappier".

 While not a tremendous difference, it makes a difference and it does add
up.

 I still find it amazing even today how much user perception is the
difference between a "slow" vs "fast" app.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Tuesday, January 13, 2015 02:21 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] System resource exceeded. Error No 3035

Hi Jim

OK, then I did the timing, and I would be careful building a "miracle
worker" status on this.

Even though the time to set DBEngine(0)(0) is zero, the time to set
CurrentDb is 0.43 ms.
Now, this a Xeon powered workstation but I doubt any newer normal
workstation would run slower than a millisecond. That's not detectable for
any user. I believe it did in the days of A97 but not today.

As you never would set CurrentDb in a loop, I think I will leave all my old
code as is.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] På vegne af Jim Dettman
Sendt: 12. januar 2015 23:31
Til: 'Access Developers discussion and problem solving'
Emne: Re: [AccessD] System resource exceeded. Error No 3035


 The difference is about an order of a magnitude, which I checked many years
ago (like A97 days). 

 Haven't bothered to check since then.  I always use the routine in the
article.

  I can say that on a number of inherited DB's, it's one of the first things
I do (swap out all currentdb()'s with CurDB()) and I always get a comment
from the users about how much faster it is already.

  Between this and always holding a reference open to the BE DB's, I've
earned the title of "miracle worker", which always seems to me to be a bit
of a cheat<g>.

  I would suggest trying it...take a copy of Northwinds (or any app) and
with Find and Replace, you can change it over pretty quickly.  You will
notice a difference.

 I would add that in all these years, I've never found a down side to using
it either.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Monday, January 12, 2015 04:25 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] System resource exceeded. Error No 3035

Hi Jim

I must admit I use CurrentDb as it is easier(!) to type than DbEngine(0)(0).

> .. I do find apps using this routine to be "snappier" then those 
> without
it.  

How you done any measurements?

/gustav

________________________________________
Fra: accessd-bounces at databaseadvisors.com
<accessd-bounces at databaseadvisors.com> på vegne af Jim Dettman
<jimdettman at verizon.net>
Sendt: 12. januar 2015 22:15
Til: 'Access Developers discussion and problem solving'
Emne: Re: [AccessD] System resource exceeded. Error No 3035

 We certainly you don't want to close it as you never opened it here in the
routine.

  Also not sure why your bothering with the mdb variable.  Take a look at
this:

http://www.experts-exchange.com/Database/MS_Access/A_2072-CurrentDB-vs-dbEng
ine-Workspaces-0-Databases-0-and-an-alternative.html

  Similar to what your doing now, but a tad different and would be faster
and eliminate overhead.

Jim. 

-- 
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