Re: Persistent Connection to Speed Performance
- From: "Katherine R" <KatherineR@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 07:07:03 -0800
First of all Albert, thank you for your reply. I really don't have the
background for building databases and would never have been able to do what
(little) I have without this Discussion Group. (I've searched and read
postings until my eyes hurt. Although most of what I read is beyond my
comprehension, sometimes I get lucky.) So, it is quite possible that my
design is lacking. I think I have my tables set up and related properly,
but...
I have a copy of the FE from before I appied the "persistent connection" and
the forms open slowly each time. After applying the persistent connection
fix the forms open slowly the first time, but instantly each time after. I
can close the application and reopen and it is the same thing - forms open
slow the first time and quickly each time after. This is an improvement.
The application itself opens quickly either way, it is just the forms I am
having problems with. I am wondering if this is the way the persistent
connection fix is supposed to work - slow on opening the first form and
quickly thereafter?
I am familar with the link you provided and have applied a number of the
tips to my database some months ago. I believe the application itself was
opening slowly before applying these tips. (I set the sub datasheet Name
property on each table in the back-end database to [NONE], I set Track name
AutoCorrect info to off, I shortened the name of the backend database, I
deleted and recreated table links, and I moved the backend as close to the
network share as our IT people would allow - The path is something like
this: \\Rev001-cc\shared\ATD\BE Data
I think I even did a decompile - maybe I should try this again?)
I don't quite understand the mde thing but I'll search the group for more on
this.
"Albert D.Kallal" wrote:
> The persistent connection trick will fix performance problems due to a split
> database.
>
> However, the persist connection trick will NOT fix a poor design.
>
> However, before we try to blame the design, you might want to check out the
> following list of things:
>
> (track auto name correct is a big one, and so is the persistent connection).
>
>
> Check the following list...go through each one:
>
> http://www.granite.ab.ca/access/performancefaq.htm
>
>
> > I added the following line of code the switchboards OnOpen event -
> > DoCmd.OpenForm "frmKeepOpen", acNormal, , , , acHidden
>
> That looks good. However, if you remove this code, and open one form...and
> close it...I bet your application sill opens faster
> (in other words, I not sure the persist trick is helping you!!).
>
> Anther good suggestion would be to try a mde for each front end you put on
> each pc...(that tend to eliminate the track auto name correct issue).
>
>
> --
> Albert D. Kallal (Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKallal@xxxxxxx
> http://www.members.shaw.ca/AlbertKallal
>
>
>
.
- References:
- Re: Persistent Connection to Speed Performance
- From: Albert D.Kallal
- Re: Persistent Connection to Speed Performance
- Prev by Date: Re: Marketing Application - Tools Needed?
- Next by Date: Re: Access VBA Boot Camp?
- Previous by thread: Re: Persistent Connection to Speed Performance
- Next by thread: Re: Set a value in VB
- Index(es):
Relevant Pages
|