My 2007 is very slow, please help

[Al]

I upgraded my Access 97 database to Access 2007 finally. After upgrading, I
noticed that the database is running very slow. I made sure to disable the
Log Tracking option on the Options Menu but the database is still slow. I
compacted and repaired but nothing has changed. Does any one know of any
issue with 2007 that slows down the database, similar to the Log Tracking
when it came out in 2002?
thanks
Al

 

[Jeff Boyce]

?Split db design?
?Network speed?
?PC 'horsepower'?
?"Back-end" located on ?

There are quite a few potential factors ... more information might help
folks offer more specific suggestions.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Al]

?Split db design?

database is split be and front end. The be end is till in 97 format. only
the front end in in 2007 format.

?Network speed?

I do not know about the network speed but it is the same when they were
using 97. Some users still using the 97 front end and do not have this issue.
We are testing the upgrade on 2 computers and they are very slow even though
they are brand new with all bills and whistles.

?PC 'horsepower'?

very good, new computers

?"Back-end" located on ?

back end and front end are on a file server in the same folder.

thanks

 

[Jeff Boyce]

First off, take that front-end off the server and put a copy on each user's
PC. Having a single copy of the front-end being accessed by multiple users
(simultaneously) is a formula for a crash!

A few years back I had to migrate back-end data from Access '97 to
SQL-Server. After re-tuning the applications, performance was fine ... for
a while.

Then, suddenly, performance tanked. After several days of troubleshooting,
getting the network folks involved with sniffers, it turned out that a new
update to the network antivirus software was clobbering every single I/O
between Access and SQL-Server. Once they whitelisted the Access
applications (front-ends), performance resumed.

Is there a chance the performance and the migration to Access 2007 are
simply correlated, and not a "causal" relationship?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Al]

I do have several FEs, each is used by 2 to 5 users and we have backups. I am
not worried about that since if corrupted we can resort to on of the other
copies, we have 5 all together. Placing a stand alone copy on every machine
is out of the question. It will be a nightmare to maintain.

Is there a chance the performance and the migration to Access 2007 are
simply correlated, and not a "causal" relationship?

Will that was the premise of my question. I had a client that I upgraded his
database from 97 to 2002 and as soon as I did that, the performance went to a
crawl. later I found out that the culprit was the track Name Autocorrect
option on the option menu. As soon as I unchecked it. The database went back
to its normal speed. I was hopping that there was something similar about
2007.

 

[Jeff Boyce]

Sorry I've not been of more help. If you haven't already, consider
searching with your favorite on-line search tool for "Microsoft Access 2007"
and "performance".

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Tony Toews [MVP]]

I do have several FEs, each is used by 2 to 5 users and we have backups. I am
not worried about that since if corrupted we can resort to on of the other
copies, we have 5 all together. Placing a stand alone copy on every machine
is out of the question. It will be a nightmare to maintain.

The below mentioned Auto FE Updater will help with some of your pain.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Will that was the premise of my question. I had a client that I upgraded his
database from 97 to 2002 and as soon as I did that, the performance went to a
crawl. later I found out that the culprit was the track Name Autocorrect
option on the option menu. As soon as I unchecked it. The database went back
to its normal speed. I was hopping that there was something similar about
2007.

Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Al]

Tony,
Thank you very much for your help. My FEs are not MDEs, will this still
work? I have access security enforced.

 

[Al]

Jeff thank you very much for taking the time. I will do the search and let
you know if I came up with something interesting.
Al

 

[Tony Toews [MVP]]

Thank you very much for your help. My FEs are not MDEs, will this still
work? I have access security enforced.

Yes, the Auto FE Updater works with MDBs and handles Access security
as well. It doesn't do a good job with ADPs though.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Al]

Thank you Tony, I will try it. I have your website as one of my favorits for
long time. Great Job!

 

[Klatuu]

It is not really a nightmare to maintain. There are serveral different
Front End Auto Updates available, many of which are free.

It is more of a nightmare not to deploy your application correctly. You
will certainly suffer performance degradation and almost certainly suffer
corruption sooner or later.