My client has new machines with Windows 7. On an Access 2002 app, a
particular screen takes 90 minutes to load running under Access 2007. On
another new laptop running XP, the same screen takes about 10 seconds
running Access 2007. On a remote desktop session running Access 2002 it took
2 seconds.

Is anyone else having this problem and did you cure it?

Thanks for any help and God Bless,

Mark A. Sam

Hi Mark,

I've been running Access 2003, 2007, and 2010 under Windows XP and Windows
7. My XP machines are considerably faster because I have more RAM on most of
them, but even on a 1 GB netbook, forms are still spunky runningAccess 2010.
The difference might be a few seconds (1 sec with 3 GB and 3 sec with 1 GB
and a slower processor)

The worst form I have takes at most 20 seconds to load, but it must deal
with 12 million records.

Try, rebuilding the database by importing all the records into a new clean
database created on the target machine.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access


"Mark A. Sam" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> My client has new machines with Windows 7. On an Access 2002 app, a
> particular screen takes 90 minutes to load running under Access 2007. On
> another new laptop running XP, the same screen takes about 10 seconds
> running Access 2007. On a remote desktop session running Access 2002 it
> took 2 seconds.
>
> Is anyone else having this problem and did you cure it?
>
> Thanks for any help and God Bless,
>
> Mark A. Sam
>

I got this resolved by compacting the backend databases.

"Arvin Meyer [MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Mark,
>

> Try, rebuilding the database by importing all the records into a new clean
> database created on the target machine.

Thanks for the response Arvin. The frontend is an .mde file which is
updated everytime the user logs in to Windows. It is copied to the local
drive. Since it was working ok on XP I didn't consider that was the issue,
but probably worth making a new .mde. I got resolved, however by compacting
the backend databases.