Would it help speed things up if they upgraded to Access
As you know, most "next" versions of software as general rule runs slower,
and takes more memory, more disk space then the previous version. I think
this rule has been true for about 20 or more years. So, most of the time,
upgrading will NOT improve speed.
When is the last time you upgraded ANY software, and that new software used
less memory, and ran faster then the previous version? (I am hard pressed to
remember when this happens!!.
However, I will say that 2003 does seem to be a lot more stable then is
a2000, and I like some of the new features like themed controls.
and I converted their Front Ends to MDE files?
We are to assume that you are talking about placing a mde on each computer.
Yes, this is a very good idea. As a general rule, a mde does run a bit
better then does a mdb. However, the mde generally does NOT fix performance
problems. However, the mde is MORE stable, and cannot become un-compiled
like a mdb can. When that mdb becomes un-compiled, then you can get long
application load times, and things most certainly can get sluggish. A mde
cannot become un-compiled. Further, the mde also ignores the track-name auto
correct issue, which again you should disable. Since there is a good half
dozen reasons and advantages to run mde's over mdb files, then you should.
For example, your users thus can't modify the mde, and you also are FORCED
to distribute a version where you KNOW the code compiles. These two reasons
alone should sell you on this concept.
As far as improving performance, you don't mention if the system runs ok
with 2 users, but then slows down as you move up to 8 users. I mean, if the
system don't work well with 2 users...how can you expect it to run well with
8, or 10 users? So, after how many users does the system slow down?
The following is a excellent check list of things you need to check to make
sure you are getting maximum performance out of your network, and your
setup. The #1 trick here is to keep a persistent connection open from the
front end on each computer to the back end. Try this first. The rest of the
list of things to check is here:
http://www.granite.ab.ca/access/performancefaq.htm
So, make sure EACH workstation gets a Front end that is placed on EACH
workstation. And, as mentioned, preferably this should be a mde.
Then, try the persistent connection trick.
If after doing all of the above in the above list, you still have
performance problems, then the next steps will actually mean you need to
start looking at your designs, as that also could be the problem with
performance. If you only got 5, to 8 users, and very small data tables in
the 75,000 record range, and say perhaps 30-40 related tables, then form
load times should on average be only about 1 second, and users should not
experience any serous kinds of delay during regular use.
