split database - performance issues

[grace]

Hello, I have a split database that is located on a
central server. Once I placed the db on the server, the
performance to display and print the reports is
unacceptable (10 min or longer). I have run through and
made some changes based on the suggestions from Tony Toews
web site, which helped slightly, but performance is still
really bad. I believe it is due to our server's
limitations.

We are now thinking about placing the database on a local
server which increases performance tremendously. I would
like to load the databse once a month onto a PC and print
a number of reports. Can I do this easily with a split
database? Now that my database is split and the tables are
linked to the server location, can I change the location
of the BE file? I have tried to find this information in
Access books, but the information on how to change the
links doesn't exist in my books!

Thanks for your help.

Grace

 

[Bruce M. Thompson]

Hello, I have a split database that is located on a

central server. Once I placed the db on the server, the
performance to display and print the reports is
unacceptable (10 min or longer). I have run through and
made some changes based on the suggestions from Tony Toews
web site, which helped slightly, but performance is still
really bad. I believe it is due to our server's
limitations.

Is a copy of the FE file located on each local workstation that will be
accessing the data (BE) file? This is vital.

We are now thinking about placing the database on a local
server which increases performance tremendously. I would
like to load the databse once a month onto a PC and print
a number of reports. Can I do this easily with a split
database? Now that my database is split and the tables are
linked to the server location, can I change the location
of the BE file? I have tried to find this information in
Access books, but the information on how to change the
links doesn't exist in my books!

After you move your BE file, on the File menu, in your front-end file, point to
Get External Data, and then click Link Tables. This will allow you to re-link to
your tables in the BE file in its new location. Then copy this front-end file to
each workstation that will be accessing the BE file.

 

[grace]

Thanks for the information on moving the be file. That
helps a lot. To answer your question, yes I do have the
FE file located on each local workstation. Splitting the
database improved performance greatly on the front-end,
but when the tables are queried it is just REAL slow.

I am not desparately searching for any solutions to my
performance problem. Any thoughts on where I can look?

Thank you,
Grace

 

[Alphonse Giambrone]

Is your server located across a LAN or a WAN?
If a WAN, that is not recommended. Search Google for lots of comments, info
on that.

 

[Bruce M. Thompson]

Thanks for the information on moving the be file. That

helps a lot. To answer your question, yes I do have the
FE file located on each local workstation. Splitting the
database improved performance greatly on the front-end,
but when the tables are queried it is just REAL slow.

I am not desparately searching for any solutions to my
performance problem. Any thoughts on where I can look?

Which suggestions from Tony Toews' web site did you implement? In my opinion,
the three most common performance problems he lists are the most important to
address and give you the most bang for the buck, shown here as listed on his
page, http://www.granite.ab.ca/access/performancefaq.htm :

"- LDB locking which a persistent recordset connection fixes
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off"

Also, on the above-referenced page, he references Jet 4.0 Service Packs 4 or 5.
If you are using Access 2000, or later, make sure you are up to at least SP6. If
you haven't already, use Office Update to see make sure you are up to date.

http://office.microsoft.com/productupdates/