By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,120 Members | 1,958 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,120 IT Pros & Developers. It's quick & easy.

2000 or 2003 app slow in Access 2007 (Vista)

P: n/a
Hi all,

So I bought a new laptop 10 days ago to test my apps with Vista. (home premium)
Apparently Office 2007 is pre-installed. (a time limited but complete test version, no SP1)
So I take the opportunity to test some new features of Access2007 before actually 'stepping over'.
First thing that troubles me of course is 'the ribbon', but my question now is about speed.

I opened one of my Access 2000-apps in Access 2007.
Speed and responsiveness is bad! It appears to me like 'wading through the mud'.
Opening an unbound form takes 2-3 seconds... Closing a form also...

After converting the app to Access 2003 format speed is the same (bad)
Even after converting to Access 2007 accdb ....

In Access 2000 or Access 2003 the app is 'snappy'.

Tested with a couple of more apps, but I am getting the same results.

--Name auto correct is off
--Backend (Acc2000) with subdatasheets <none>

Tried to install SP1 but that install simply failed...
Checked references, tried decompile, tried compact, tried import in clean db and such.

Any idea's ? I must be missing something obvious here...

Arno R
Jan 19 '08 #1
Share this Question
Share on Google+
10 Replies


P: n/a
"Arno R" <ar****************@planet.nlwrote in
news:47***********************@text.nova.planet.nl :
Hi all,

So I bought a new laptop 10 days ago to test my apps with Vista. (home
premium) Apparently Office 2007 is pre-installed. (a time limited but
complete test version, no SP1) So I take the opportunity to test some
new features of Access2007 before actually 'stepping over'. First
thing that troubles me of course is 'the ribbon', but my question now
is about speed.

I opened one of my Access 2000-apps in Access 2007.
Speed and responsiveness is bad! It appears to me like 'wading through
the mud'. Opening an unbound form takes 2-3 seconds... Closing a form
also...

After converting the app to Access 2003 format speed is the same
(bad) Even after converting to Access 2007 accdb ....

In Access 2000 or Access 2003 the app is 'snappy'.

Tested with a couple of more apps, but I am getting the same results.

--Name auto correct is off
--Backend (Acc2000) with subdatasheets <none>

Tried to install SP1 but that install simply failed...
Checked references, tried decompile, tried compact, tried import in
clean db and such.

Any idea's ? I must be missing something obvious here...

Arno R
I run Office 2007 on a desktop with an Intel E6750 (dual) cpu and 2 gigs
of ram. It's fine, fast if not snappy.
But on other, older computers with a single processor it's been
gruesomely slow and I've uninstalled it and reinstalled Office 2000, 2002
or 2003 depending on what seemed suitable (for instance, Office 2000 on a
Celeron 1.7).
If I were going to work with Office 2007 extensively I'd look at a quad
processor, and a 64 bit operating system so I could access several gigs
of ram.
But maybe I'm doing something wrong.

--
lyle fairfield

I will arise and go now,
For always night and day
I hear lake water lapping
With low sounds by the shore;
While I stand on the roadway
Or on the pavements gray,
I hear it in the deep heart's core.
- Yeats
Jan 19 '08 #2

P: n/a
One would assume a brand new machine would be reasonably fast, but it may be
that you're getting hit with a double whammy!

I just read a paper, I think it was from ZDNet, that reported that many, many
new laptops were simply not powerful enough to run Vista with all its bells
and whistles. And I've seen reports from users, running various PCs, many of
them state of the art and powerful, complaining of ACC2007 being god awful
slow in running 2000-2003 apps. What I haven't seen is anyone who's found an
answer to the problem!

Allen Browne has been doing a lot of testing with 2007 and upgrading from
previous versions, perhaps he'll wander by and enlighten us!

Linq

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

Jan 20 '08 #3

P: n/a
Each version of Access is slower than the one before on the same hardware.
Like the cynical Wirth's law:
Software gets slower faster than hardware gets faster.
(Source: http://en.wikipedia.org/wiki/Wirth%27s_law )
So, yes, A2007 is slower than previous versions.

Similarly, Vista is much slower that WinXP for some operations (particularly
deleting large files.) And the drivers are much less developed. When Vista
was first released, A2007 was so slow in design view, that there was almost
1 second delay in tabbing from one property to the next, and I constantly
found myself typing into the wrong property. This was largely solved when
nVidia released new drivers.

Office 2007 SP1 also addressed some performance issues. IMHO, A2007 without
SP1 is unusable - not from a performance perspective, but just unreliable.
None of my non-trivial apps would work reliably for all cases until SP1 was
released, so I would certainly not recommend it for any purpose beyond
experiementation (which was the OP's goal.) Some issues were not solved in
SP1 (e.g. assigning a specific printer to a report), but it's now quite
usable (though not hugely faster than the original release.) A major fix was
the delay when starting A2007 after using a previous version (down from 3.5
minutes to 18 seconds on my machine.)

There are other issues running Access (any version) under Vista, like
RunAsAdministrator, avoiding the virutalized folders, avoiding off-line
folders, and poor performance of intensive queries:
http://allenbrowne.com/VistaCPULoad.html

The OP was running on a laptop. As Linq Adams says, many laptops have
limited grunt, even more limited RAM, and poor graphics processing (stealing
even more system RAM.)

Suggestions:

1. Turn Aero off. You can live without the pretty translucent windows if the
laptop is more responsive.

2. Remove the "free" software that came installed on your computer.
Particuarly, the security stuff from Norton and others mean that the files
are being dragged through mud off your slow-spinning notebook drive.

3. If you have less than 2MB of RAM, consider adding more.
If you cannot do that, reduce the number of programs open at once.

You have probably already read Tony's suggestions for Access performance:
http://www.granite.ab.ca/access/performancefaq.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Linq Adams via AccessMonster.com" <u28780@uwewrote in message
news:7e7844d18df8a@uwe...
One would assume a brand new machine would be reasonably fast, but it may
be
that you're getting hit with a double whammy!

I just read a paper, I think it was from ZDNet, that reported that many,
many
new laptops were simply not powerful enough to run Vista with all its
bells
and whistles. And I've seen reports from users, running various PCs, many
of
them state of the art and powerful, complaining of ACC2007 being god awful
slow in running 2000-2003 apps. What I haven't seen is anyone who's found
an
answer to the problem!

Allen Browne has been doing a lot of testing with 2007 and upgrading from
previous versions, perhaps he'll wander by and enlighten us!

Linq
Jan 20 '08 #4

P: n/a
On Jan 19, 10:25 pm, "Allen Browne" <AllenBro...@SeeSig.Invalid>
wrote:
Each version of Access is slower than the one before on the same hardware.
Like the cynical Wirth's law:
Software gets slower faster than hardware gets faster.
(Source:http://en.wikipedia.org/wiki/Wirth%27s_law )
So, yes, A2007 is slower than previous versions.

Similarly, Vista is much slower that WinXP for some operations (particularly
deleting large files.) And the drivers are much less developed. When Vista
was first released, A2007 was so slow in design view, that there was almost
1 second delay in tabbing from one property to the next, and I constantly
found myself typing into the wrong property. This was largely solved when
nVidia released new drivers.

Office 2007 SP1 also addressed some performance issues. IMHO, A2007 without
SP1 is unusable - not from a performance perspective, but just unreliable.
None of my non-trivial apps would work reliably for all cases until SP1 was
released, so I would certainly not recommend it for any purpose beyond
experiementation (which was the OP's goal.) Some issues were not solved in
SP1 (e.g. assigning a specific printer to a report), but it's now quite
usable (though not hugely faster than the original release.) A major fix was
the delay when starting A2007 after using a previous version (down from 3.5
minutes to 18 seconds on my machine.)

There are other issues running Access (any version) under Vista, like
RunAsAdministrator, avoiding the virutalized folders, avoiding off-line
folders, and poor performance of intensive queries:
http://allenbrowne.com/VistaCPULoad.html

The OP was running on a laptop. As Linq Adams says, many laptops have
limited grunt, even more limited RAM, and poor graphics processing (stealing
even more system RAM.)

Suggestions:

1. Turn Aero off. You can live without the pretty translucent windows if the
laptop is more responsive.

2. Remove the "free" software that came installed on your computer.
Particuarly, the security stuff from Norton and others mean that the files
are being dragged through mud off your slow-spinning notebook drive.

3. If you have less than 2MB of RAM, consider adding more.
If you cannot do that, reduce the number of programs open at once.

You have probably already read Tony's suggestions for Access performance:
http://www.granite.ab.ca/access/performancefaq.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Linq Adams via AccessMonster.com" <u28780@uwewrote in messagenews:7e7844d18df8a@uwe...
One would assume a brand new machine would be reasonably fast, but it may
be
that you're getting hit with a double whammy!
I just read a paper, I think it was from ZDNet, that reported that many,
many
new laptops were simply not powerful enough to run Vista with all its
bells
and whistles. And I've seen reports from users, running various PCs, many
of
them state of the art and powerful, complaining of ACC2007 being god awful
slow in running 2000-2003 apps. What I haven't seen is anyone who's found
an
answer to the problem!
Allen Browne has been doing a lot of testing with 2007 and upgrading from
previous versions, perhaps he'll wander by and enlighten us!
Linq
I run Vista on two machines. It is fast on both, and I do not
experience the problems you describe. But I did remove ALL trial and
free software upon receiving the machines (one had nothing but Roxio
the removal of which is a special chore) and I have been careful to
download and install every available update to every application and
service and driver running on the machines.

But the most significant improvements for me came after I downloaded
and installed the latest BIOS for my respective machines; one machine
was very much faster after that.

I thought Vista was a bad joke when it first came out. Now, I'm quite
happy with it, and would put it on all my Vista capable machines were
it not for problems it has with things like HotSyncing to a Palm
Pilot, and communicating with a Garmin GPS receiver. My only unsolved
puzzle is that on one machine the Windows Security Centre reports that
McAffee antivirus is installed, updated and running. I can't find
McAffee sofware on the hard drive, nor any indication in Task Manager
that it is running. Maybe it's hidden in some virtual place; in my
spare time, if I ever have any, I'll search.
I recommend that developers first running Vista learn about the
AppData folders; for a while they 100% baffled me. Now it's just 96%.
Jan 20 '08 #5

P: n/a
rkc
Allen Browne wrote:
A major fix was the delay when starting A2007 after
using a previous version (down from 3.5 minutes to 18 seconds on my
machine.)
The problem I have with A2007 is that it corrupts my installation
of A2002. Control events are not recognized in A2002 after I run
A2007. I have to do a repair from the Control Panel each time to
fix it. Very annoying.

Windows Vista with a stand alone copy of Access 2007.
Jan 20 '08 #6

P: n/a
Perhaps someone else can suggest something.
I have not observed that.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Arno R" <ar****************@planet.nlwrote in message
news:47***********************@text.nova.planet.nl ...
==New test:
A new database with *only* these three forms (and some basic modules) runs
snappy.
When I simply import more objects (like 50 query's) from the original db the
very same forms become 'muddy' (slow).
Corruption ?? I can't find anything.

What is happening ??
Is Access (or is it Vista ??) indexing the whole lot ??
I turn my anti-virus (Avast) software off ==no difference.

Arno R

Jan 20 '08 #7

P: n/a
On Jan 20, 1:27 am, lyle <lyle.fairfi...@gmail.comwrote:
My only unsolved
puzzle is that on one machine the Windows Security Centre reports that
McAffee antivirus is installed, updated and running.
Solved now.
Jan 21 '08 #8

P: n/a
On Jan 20, 5:56 pm, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
Perhaps someone else can suggest something.
I have not observed that.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Arno R" <arracomn_o_s_p_...@planet.nlwrote in message

news:47***********************@text.nova.planet.nl ...
==New test:
A new database with *only* these three forms (and some basic modules) runs
snappy.
When I simply import more objects (like 50 query's) from the original db the
very same forms become 'muddy' (slow).
Corruption ?? I can't find anything.

What is happening ??
Is Access (or is it Vista ??) indexing the whole lot ??
I turn my anti-virus (Avast) software off ==no difference.

Arno R
To see if it's the database, or Access, you could download Northwind
2007 and see if it is snapply or muddy. I think if you choose Open ->
New some template headings appear and if you click on Sample, then the
Northwind 2007 download icon is shown. FWIW, Northwind 2007 is
"snappy" for me.
But in other dbs I have had the experience of imported objects being
muddy. IIRC saving them as text, and loading them back in Access 2007
helped. With queries, maybe you can just copy and import the SQL
string?
Jan 21 '08 #9

P: n/a

"lyle" <ly************@gmail.comschreef in bericht
news:eb**********************************@c23g2000 hsa.googlegroups.com...
On Jan 20, 5:56 pm, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
>Perhaps someone else can suggest something.
I have not observed that.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Arno R" <arracomn_o_s_p_...@planet.nlwrote in message

news:47***********************@text.nova.planet.n l...
==New test:
A new database with *only* these three forms (and some basic modules) runs
snappy.
When I simply import more objects (like 50 query's) from the original db the
very same forms become 'muddy' (slow).
Corruption ?? I can't find anything.

What is happening ??
Is Access (or is it Vista ??) indexing the whole lot ??
I turn my anti-virus (Avast) software off ==no difference.

Arno R

To see if it's the database, or Access, you could download Northwind
2007 and see if it is snapply or muddy. I think if you choose Open ->
New some template headings appear and if you click on Sample, then the
Northwind 2007 download icon is shown. FWIW, Northwind 2007 is
"snappy" for me.
But in other dbs I have had the experience of imported objects being
muddy. IIRC saving them as text, and loading them back in Access 2007
helped. With queries, maybe you can just copy and import the SQL
string?
I finally did find the cause of the slowness!!
Well it's the database indeed... (I allready noticed that Northwind 2007 is snappy)

For several years now I develop my apps with 'the Internet hand' showing.
The 'hand' shows when you move the mouse over a clickable control.
This 'hand' is invoked by simply setting the property 'Hyperlinksubaddress' to a space.
See: http://groups.google.nl/group/comp.d...3f55b7c7ffc50a
Btw: I see that Access 2007 has a new property (cursor on ... 'hyperlinkhand' ) to do the very same...

==Simply removing the spaces I use everywhere for the 'Hyperlinksubaddress' solves the speed-issue.
==My app is 'snappy' as is was before ! Problem solved!
So I am glad my new laptop *is* speedy enough to run Vista and Access 2007.

Still strange though that starting with *only* 3 forms (with hyperlinksubaddress property set to a space) the app is
speedy enough, while adding some query's slows down the forms ....
I tested this again, and I can repeat it over and over again. Nevertheless: problem is solved.

New problem:
Now it seems that I need different apps for Access 2007 and earlier versions...
(When I remove all the spaces, the 'hand' wil not show when using Acc2k or Acc2003...)

Again I tried to install SP1 for Office 2007 to see if the issue is solved with SP1.
Maybe because I have an evaluation version the update fails ??

Would anyone here be willing to check the behaviour of spaces in the hyperlinksubaddress property with Access2007 SP1??
Thanks much

Arno R

Jan 21 '08 #10

P: n/a

"news.planet.nl" <ar****************@planet.nlschreef in bericht news:47***********************@text.nova.planet.nl ...

Again I tried to install SP1 for Office 2007 to see if the issue is solved with SP1.
Maybe because I have an evaluation version the update fails ??

Would anyone here be willing to check the behaviour of spaces in the hyperlinksubaddress property with Access2007 SP1??
Thanks much

Arno R

Sorry, previous message posted from my laptop with newsaccount not properly setup ...

I still would like to know if the speed-issue I described in this thread is solved with Access 2007 SP1.
Anyone here willing to test this ??

Speed-issue:
(Access2007 and Vista).
Setting the property hyperlinksubaddress of a commandbutton to a space or to #, results in a delay of a few seconds here.
Behaviour seems to be the same with mdb or accdb format.

Thanks
Arno R
Jan 22 '08 #11

This discussion thread is closed

Replies have been disabled for this discussion.