MonsterMaxx
Registered User.
- Local time
- Yesterday, 16:36
- Joined
- Sep 24, 2008
- Messages
- 15
When I go to the field I take my database with me on the laptop.
It's a tabbed thing so the one main form contains nearly everything. So when I open the main form it's likely opening every form and running every query in the database to get launched.
When I open the form on my workstation it takes a few seconds. It's slow, no doubt doing a lot of calculations, but it takes 5 seconds tops.
When I open it on my laptop it takes 2-3 minutes, the status bar shows 'calculating...'
The laptop is pretty much state of the art (core 2 duo 2.0) and the workstation is 5 years old (dual 3ghz xeon.) The laptop is considerably faster on any benchmark by a factor of 3-4 times.
The workstation does open the file over the network since the database sits on the file server and it's array is likely a bit faster (twice maybe) than the laptop's drive. But the file size is only 2.5MB.
When I open the networked file with the laptop it does respond quite a bit faster than if I open it off the laptop's local drive, but still shows 'calculating...' for a long time and is not as fast as the old workstation.
It's the same Access 2003 install on both machines.
In development I can live with it, but this is clearly not going to be acceptable when I release it.
What could be causing this performance hit on the laptop? What can I do about it?
It's a tabbed thing so the one main form contains nearly everything. So when I open the main form it's likely opening every form and running every query in the database to get launched.
When I open the form on my workstation it takes a few seconds. It's slow, no doubt doing a lot of calculations, but it takes 5 seconds tops.
When I open it on my laptop it takes 2-3 minutes, the status bar shows 'calculating...'
The laptop is pretty much state of the art (core 2 duo 2.0) and the workstation is 5 years old (dual 3ghz xeon.) The laptop is considerably faster on any benchmark by a factor of 3-4 times.
The workstation does open the file over the network since the database sits on the file server and it's array is likely a bit faster (twice maybe) than the laptop's drive. But the file size is only 2.5MB.
When I open the networked file with the laptop it does respond quite a bit faster than if I open it off the laptop's local drive, but still shows 'calculating...' for a long time and is not as fast as the old workstation.
It's the same Access 2003 install on both machines.
In development I can live with it, but this is clearly not going to be acceptable when I release it.
What could be causing this performance hit on the laptop? What can I do about it?
Last edited: