2000 or 2003 app slow in Access 2007 (Vista)

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.=20
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

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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

"Arno R" wrote in
news:47926660$0$25476$ba620dc5@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
>
> 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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

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" wrote 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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

I guess that's Microsoft's definition of progress!? Another obscure
problem that I've come across running A2003 or A2007 under Vista is a
chart bug that I've posted about before. Another contributor to this
forum had seen it as well. The problem manifests in charts on
reports. The chart either expands to the right off the edge of the
report or is truncated and doesn't show all the way to the right hand
side of the chart object.

I thought I'd fixed it by changing the "Size Mode" of all the charts
to "Clip" but the problem still appears at times. In design view I've
noticed that when I double click a chart to open the chart object to
resize it, I can still see a portion of the chart replicated on the
right hand side outside the chart object border. This explanation may
not be the best, but the problem only appears under Vista. A user of
one of my databases called me when he acquired a new Vista machine and
complained of the problem, so it's not just my machine. I fixed the
offending charts by fiddling around with their size but there was
nothing logical to the fix. These problems don't manifest under Window
XP.

Re: 2000 or 2003 app slow in Access 2007 (Vista)

"Allen Browne" schreef in bericht =
news:4792bf15$0$17205$5a62ac22@per-qv1-newsreader-01.iinet.n et.au...
> Each version of Access is slower than the one before on the same =
hardware.=20
> 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.
>=20
> Similarly, Vista is much slower that WinXP for some operations =
(particularly=20
> deleting large files.) And the drivers are much less developed. When =
Vista=20
> was first released, A2007 was so slow in design view, that there was =
almost=20
> 1 second delay in tabbing from one property to the next, and I =
constantly=20
> found myself typing into the wrong property. This was largely solved =
when=20
> nVidia released new drivers.
>=20
> Office 2007 SP1 also addressed some performance issues. IMHO, A2007 =
without=20
> SP1 is unusable - not from a performance perspective, but just =
unreliable.=20
> None of my non-trivial apps would work reliably for all cases until =
SP1 was=20
> 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=20
> SP1 (e.g. assigning a specific printer to a report), but it's now =
quite=20
> usable (though not hugely faster than the original release.) A major =
fix was=20
> the delay when starting A2007 after using a previous version (down =
from 3.5=20
> minutes to 18 seconds on my machine.)
>=20
> There are other issues running Access (any version) under Vista, like=20
> RunAsAdministrator, avoiding the virutalized folders, avoiding =
off-line=20
> folders, and poor performance of intensive queries:
> http://allenbrowne.com/VistaCPULoad.html
>=20
> The OP was running on a laptop. As Linq Adams says, many laptops have=20
> limited grunt, even more limited RAM, and poor graphics processing =
(stealing=20
> even more system RAM.)
>=20
> Suggestions:
>=20
> 1. Turn Aero off. You can live without the pretty translucent windows =
if the=20
> laptop is more responsive.
>=20
> 2. Remove the "free" software that came installed on your computer.=20
> Particuarly, the security stuff from Norton and others mean that the =
files=20
> are being dragged through mud off your slow-spinning notebook drive.
>=20
> 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.
>=20
> You have probably already read Tony's suggestions for Access =
performance:
> http://www.granite.ab.ca/access/performancefaq.htm
=20
Thanks for the suggestions Allen. (also thanks to others who replied)
1 I turned Aero off, makes no noticeable difference (still have it off, =
because I heard/read it 'eates' resources)
2 I did remove all the Norton Security Software immediately. (I am =
using Avast at home)
3 I do have 2 Gigs of Ram on my laptop (Acer Extensa 5210)
I also did read Tony's suggestions. (Not for the first time...)

I am very careful in setting up this system.=20
I know it is not the best/fastest laptop one can buy, but 'heavy' =
software like Adobe Lightroom runs allright.
The sample Northwind 2007 database also runs fine ...

I am still thinking that opening or closing an *unbound* form would =
*not* have to take seconds.
==> New test:
A new database with *only* these three forms (and some basic modules) =
runs snappy.=20
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 ??=20
Is Access (or is it Vista ??) indexing the whole lot ??
I turn my anti-virus (Avast) software off ==> no difference.

Arno R

Re: 2000 or 2003 app slow in Access 2007 (Vista)

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.

Re: 2000 or 2003 app slow in Access 2007 (Vista)

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" wrote in message
news:47935f78$0$25474$ba620dc5@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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

On Jan 20, 1:27 am, lyle wrote:
> My only unsolved
> puzzle is that on one machine the Windows Security Centre reports that
> McAffee antivirus is installed, updated and running.

Solved now.

Re: 2000 or 2003 app slow in Access 2007 (Vista)

On Jan 20, 5:56 pm, "Allen Browne" wrote:
> 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" wrote in message
>
> news:47935f78$0$25474$ba620dc5@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?

Re: 2000 or 2003 app slow in Access 2007 (Vista)

"lyle" schreef in bericht
news:eb78f1bd-7c87-4230-b62f-5363dbd7b380@c23g2000hsa.google groups.com...
> On Jan 20, 5:56 pm, "Allen Browne" wrote:
>> 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" wrote in message
>>
>> news:47935f78$0$25474$ba620dc5@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?

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.databases.ms-access/msg/1 c3f55b7c7ffc50a
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

Re: 2000 or 2003 app slow in Access 2007 (Vista)

"news.planet.nl" schreef in bericht =
news:47946777$0$25501$ba620dc5@text.nova.planet.nl...
>=20
> 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 ??
>=20
> Would anyone here be willing to check the behaviour of spaces in the =
hyperlinksubaddress property with Access2007 SP1??
> Thanks much
>=20
> 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=20
Arno R