Too slow

[Ruben Granados]

Hi, I have a database of 1.8M I split it, Compact and make
the .MDE
now i'm running the front end from my desktop and the back
end is on a file server.
the database is going to be used every day for about
25users. each user will add new records every day about
30records per day. I need monthly reports expecting about
900 records per report.
Now that I'm testing it's too slow. let's say a 2page
report takes 1minute to open. This didn't happen before
the most it took 10secs.
How can I improve performance?

 

[Albert D. Kallal]

Often when you split, some performance is lost.

However, the amount lost is usually quite small as compared to running a non
split system. (we are talking about using a network in both cases).

The best, and #1 trick is to make sure that ALWAYS a connection to the back
end is opened. So, at the start-up, either have some code that opens a dummy
table in the back end, or even simple form that you open.

You can make a instant test of this. Go in your front end, and open a table
to view records. Now minimize this table, and try running your report. The
performance is back. Of course, you don't want to train your users to do
such a funny task, so all you have to do is make sure that a table (any
table) is kept open across the network.

Try the above. The other list of things to check can be found here, and it
is a real gem in terms of what you need to check, or set to get performance
good in your case:

Check out:
http://www.granite.ab.ca/access/performancefaq.htm