Re: Access Slow Over Network
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Tue, 12 Feb 2008 19:58:02 -0700
"Powlaz" <Powlaz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BC603B54-5A82-47CB-AC3A-77E68CC08E71@xxxxxxxxxxxxxxxx
4. The owner of the company has talked to the Access application
developer
about separating the front end so it can be installed locally but . . .
what do you mean "but...."
Your your company seems willing to
be spending some time on fixing performance problems, but not fix how you
do things???? I will bet for the last fifteen plus years you've always
installed software on each
computer WorkStation. Somehow, now you're suggesting to throw out all of
this time honored approach, and for some reason you not willing to install
the software on each WorkStation like you've done for years and years with
virtually every other application that you have.
The old story about leaving a horse to water comes to mind here.
I guess the problem here is that you're trying to come here and look for
some good solid advice, yet at the same time ignore good solid advice?
Read my following
article and splitting, as it not only tells you to split your database, but
explains why. It is the ***why*** you split apart is that you need to grasp
here.
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
The above explains the difference between applications that you create, and
the concept of a simple data file that an application consumes.
I should point out that *often* in many cases splitting does not help, nor
does it solves your performance problems. However it most certainly affects
the reliability of your operations in a significant way. It simply a good
practice to adopt. I guess it kind of problems beget problems, and the
solution here is the overall approach that you take goes a long way to
solve the many challenges that the IT industry will present to you.
Anyway, the definitive list of things "setup" wise for performance is
outlined here
http://www.granite.ab.ca/access/performancefaq.htm
Go through the above list of suggestions carefully, and then go through it
again.
If after going through the above list your performance problems remain, then
it is likely the design of the application that is causing the poor
performance, and not your particular network setup. is also possible that
your application simply is too large and complex and has too much data for
your given setup. for example does the application done well with two users,
but act you increase the workload to four users that's 100% increase, does
the application significantly slow down?
Software is very much a like a construction project, and if you don't get
the foundations of the building correct, then the rest the software you
build around it often will cause poor performance. It goes without saying
that good performing applications are the results of good solid designs,
and throwing more hardware at these applications usually does not fix
the performance issues at hand.
So, check out that performance list, as there is a significant number of
settings and things that can significantly changed how the application
performs.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- Prev by Date: Re: Access Slow Over Network
- Next by Date: [Visitbazaar.com] Internet Surfing is now become more timeless with our MyWindow feature.....
- Previous by thread: Re: Access Slow Over Network
- Next by thread: RE: Access Slow Over Network
- Index(es):
Relevant Pages
|
