I've had Access 2007 for three years. All of a sudden it is taking
minutes at a time to perform simple actions in form design view such
as moving a control, maximizing the form window, moving back and forth
from design to form or layout view, etc.

This doesn't only happen with db's created with earlier versions of
Access. Opening and closing the db helps for only a few minutes before
it starts to happen again. Same goes for compact/repair.

Not entirely sure when this started happening but I wonder if it could
possibly have something to do with something that happened a few weeks
ago: I was checking out chart creation in Access forms and pivot table
view. I can't remember exactly what, but I clicked on something and
got a message saying that feature was not installed. I told it to
install and I think there was a crash in the middle of the
installation process. Everything seemed to work okay immediately after
that and I didn't need to do anything more with charts, so I forgot
about it.

Maybe I need to reinstall Access? If I do so, does that count as a
second computer toward the maximum # of installations on this
license?

Thanks for your help.

I have a similar problem. What usually happens is that the first few
changes I make in Design View are at a speed one would expect, then it
starts moving slow as molasses. Maximizing a form in Design View takes
30 seconds or so. But if I close Access, then re-open and make more
changes, it moves at normal pace, at least for the first few design
changes, then it slows down again. On Friday, changes to a Report,
such as editing a label, were excruciatingly slow, too. I don't work
in Reports much but I am sure this is not how it should be working. I
NEVER had this problem in A2003 or A2010 (I have both at home). In
fact, the only time I've noticed this problem is in A2007 on my work
PC. I've used A2007 on my wife's work PC before and never noticed the
issue.

Somewhere I read that this had to do something with being hooked up to
a networked PC. So I changed my default printer at work to PDFCreator
instead of the network printer but the issue still occurred.

I would love to know how to make this go away.

Steve

On Apr 17, 9:16*am, SteveJ <jcptc... (AT) earthlink (DOT) net> wrote:
That is pretty much exactly what I'm experiencing. I'm on a wireless
network for internet purposes, am not using network file sharing, and
my printer is on a local USB connection. So I don't think the
networking is the issue. I tried running an Office 2007 installation
repair and that didn't help at all. Still wondering if reinstalling
Access or Office needs to be the next step.

Do you have SP2 applied?
What is your back end?
Prior to SP2 there was an issue similar to what you describe when using SQL
Server back end. It was resolved with a hot fix, then with SP2.

--

AG
Email: npATadhdataDOTcom


"septimus" <ovengravel (AT) yahoo (DOT) com> wrote

On Apr 19, 1:25*pm, "agiamb" <NOSPAMagi... (AT) newsgroup (DOT) nospam> wrote:
I take it you are referring to MS Office 2007 SP2? I checked an it is
not installed. We are not using a SQL server backend. It is a split
Access DB with the backend on a share drive. Operating system is XP.

Steve

I'm not using a separate backend at all on this project. I'm just
running queries and dumping the data into Excel.

Not sure about SP2, I tried to figure out whether I had it but I
haven't been able to find a way that works. Is there an easy way to
check whether it's been installed?

I did try reinstalling Office and it doesn't seem to have done much to
solve the problem.

Thanks.


On Apr 21, 6:09*pm, SteveJ <jcptc... (AT) earthlink (DOT) net> wrote:

Office button > Access Options > Resources > About

--

AG
Email: npATadhdataDOTcom


"septimus" <ovengravel (AT) yahoo (DOT) com> wrote

I'm not using a separate backend at all on this project. I'm just
running queries and dumping the data into Excel.

Not sure about SP2, I tried to figure out whether I had it but I
haven't been able to find a way that works. Is there an easy way to
check whether it's been installed?

I did try reinstalling Office and it doesn't seem to have done much to
solve the problem.

Thanks.


On Apr 21, 6:09 pm, SteveJ <jcptc... (AT) earthlink (DOT) net> wrote:

Ah, thanks AG. I do have SP2.
So what else could be causing this?


On Apr 22, 3:47*pm, "agiamb" <NOSPAMagi... (AT) newsgroup (DOT) nospam> wrote:

"septimus" wrote in message
news:4a4e3cfd-84ae-4200-8e16-8496344541c6 (AT) q30g2000vbs (DOT) googlegroups.com...

OK assuming this is not a split database, then the next couple of things to
check are if you're using an unattached or network printer?
Access constantly queries the printer for information about control layout
for both forms and reports. So if a printer is offline or not attached, or
is a network printer, this can be a source of delays .

In fact as a general Rule I now own set my default printer to a local
default PDF printer to prevent the above problem.

Another option to turn off is track name auto correct, as this can over time
be a source of delays during development - so I would disabled this feature
also.

And while your database may not be split, it's possible that you have
several table links in the table view that are network based or linked to
external data sources. Thus again this has been known to be a source of
delays during development.

If the above idea does not fix this, then work you way though the list here:

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

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

I heard about the network printer thing, too. I mistyped in my first
post and wrote network PC, but I meant to type network printer. I do
have a network printer. I've set up a form in db that changes the
default printer to PDFCreator but it didn't seem to help. Do I need to
reboot or anything after I set the printer to PDFCreator. I'll try it
again on Monday.