T
Tom McNally
We recently migrated a number of databases from Office 97 to Office XP. The
applications were originally written in Office 97, and I used the wizard to
convert them (all recordset and database objects are DAO and specified as
such in VB). Outside of the usual new references added during or because of
the conversion, the databases on the whole seem to be much more sluggish
than in the past. For examp, when I view a table from the database window,
seems to take about 3-5 seconds to open, regardless of if the table has 10
rows or 50K! Queries on the other hand open almost instantaneously (assume
Jet has a lot to do with it). On faster machines (P4s or Athalon XPs) with
at least 512M of memory, the delay is unnoticeable, but most of the machines
my client and our development team use unfortunately are PIIIs with 256M
memory. I suspect XP Office has a lot of overhead. In 97 opening raw table
views were much faster. Needless to say, users are getting annoyed. The
OSs are now all XP Professional, with all latest SP applied both for
OfficeXP and XP Pro.
Also, stored, complex queries that were used for exporting data to Excel
often will have the "Export" option greyed-out. So we have to create a
maketable query, save the damn thing and then export the table. Why would
this be so? Office 97 and Office 2K didn't pose this issue ever.
Have been using Access for about 10 years and would like to know what the
new memory requirements are so I can offer some realistic advice to my
client (and our lame, cheap IT dept!). Would upping the memory on the boxes
to 512M dramatically improve responsiveness, or is it back to new processor
+ memory + motherboard + disk access speed (ie, a new updated PC?)
I suspect the latter, but budgets are tight for new boxes. Memory is still
cheap, time isn't, however.
Thanks!
Tom
applications were originally written in Office 97, and I used the wizard to
convert them (all recordset and database objects are DAO and specified as
such in VB). Outside of the usual new references added during or because of
the conversion, the databases on the whole seem to be much more sluggish
than in the past. For examp, when I view a table from the database window,
seems to take about 3-5 seconds to open, regardless of if the table has 10
rows or 50K! Queries on the other hand open almost instantaneously (assume
Jet has a lot to do with it). On faster machines (P4s or Athalon XPs) with
at least 512M of memory, the delay is unnoticeable, but most of the machines
my client and our development team use unfortunately are PIIIs with 256M
memory. I suspect XP Office has a lot of overhead. In 97 opening raw table
views were much faster. Needless to say, users are getting annoyed. The
OSs are now all XP Professional, with all latest SP applied both for
OfficeXP and XP Pro.
Also, stored, complex queries that were used for exporting data to Excel
often will have the "Export" option greyed-out. So we have to create a
maketable query, save the damn thing and then export the table. Why would
this be so? Office 97 and Office 2K didn't pose this issue ever.
Have been using Access for about 10 years and would like to know what the
new memory requirements are so I can offer some realistic advice to my
client (and our lame, cheap IT dept!). Would upping the memory on the boxes
to 512M dramatically improve responsiveness, or is it back to new processor
+ memory + motherboard + disk access speed (ie, a new updated PC?)
I suspect the latter, but budgets are tight for new boxes. Memory is still
cheap, time isn't, however.
Thanks!
Tom