Queries using what Add-On?

[BanditWk]

I know that the subject doesn't give much to go on, so let me explain.

I have a database with a front-end database that the users interface with, linked to several back-end databases on one server (we wanted to keep the databases under 100 Meg).

I have one Report that utilizes 6 queries to get the information and, within that report, summarizes percentages, etc, etc.

Last week, the Report was quick. We rebuilt the server Thursday and installed only what we thought was needed from Microsoft Office Professional to make the server work. We must've forgot something, because now that same report takes a LOT of CPU cycles (maxes out two 1.0 Gigahertz processors) and takes time for it to come up. Is there something in the Microsoft Office that we absolutely NEED to make sure that the Queries are running efficiently like it was before?

Please advise. Thanks in advance.
Roy McCafferty
aka BanditWk

Las Vegas, NV
roy@cccamerica.org
RLMBandit@aol.com (private)

"I do this because I know I can and I'm bored at work - no need to send flowers, wine, dinner, or coffee... Just send me a smile to show me that I've helped." ~ Roy McCafferty, seen on a corn

 

[scriverb]

If your queries are in your front-end database and have not changed since your server rebuild then I suspect that the simple server rebuild and possible renaming is the culpret.

ACCESS Jet will initially at each workstation re-optimize its queries if it suspects that the database structure has changed. This can include linked tables where the UNC linkeage identifier has changed. If you went from one server name to another then each and every copy of the front-end database will reoptimize the queries. I experienced this problem when we switched our servers over to Windows 2000 and our Server folks renamed the servers. So, my queries thought that I had changed all of the database structure and the next time each query ran on each Users desktop(3500) the application sat there and reoptimized the queries. Can take quite a while if the database is large and complex, i.e. lots of indexes, links etc.

Just a thought because it sounded like our problem a little.

Bob Scriver