Prev: How do I populate a subform field with a value from the main form?
Next: Adding lookup to a exsisting form
From: Mark A. Sam on 17 May 2010 15:31 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
From: Arvin Meyer [MVP] on 17 May 2010 22:34 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" <MarkASam(a)EmEssEn.Com> wrote in message news:%23SaAAdf9KHA.5476(a)TK2MSFTNGP06.phx.gbl... > 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 >
From: Mark A. Sam on 18 May 2010 06:40 I got this resolved by compacting the backend databases.
From: Mark A. Sam on 18 May 2010 06:42
"Arvin Meyer [MVP]" <arvinm(a)mvps.invalid> wrote in message news:%23kBniKj9KHA.3592(a)TK2MSFTNGP05.phx.gbl... > 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. |