G
GW Hogg
I converted a set of Access 2000 queries to Access 2003.
A macro set the whole process off-
A query creates a table of part numbers, then runs a series of make-table
queries using the first table. Then one query combines the data from the
created tables, which I then export to Excel.
This whole process took 20 min. in Access 2000, but now takes 6 hours in
Access 2003. The slow down seems to happen everytime I link to a created
table. For if I remake one query to not use a table, but look up the data, it
takes seconds instead of minutes.
I have made sure that any tables created are saved in the 2003 format.
I have tried Indexing and setting a Primary Key; no change
Does anyone know what might be slowing each query down, when it access a
'made' table?
Is there something I am missing during the conversion process? (I did delete
all the 'made tables' after the conversion)
I do not relish the idea of re-writting all the queries, since it would
entail making six different versions, one for each group that uses it.
Thanks
GW Hogg
A macro set the whole process off-
A query creates a table of part numbers, then runs a series of make-table
queries using the first table. Then one query combines the data from the
created tables, which I then export to Excel.
This whole process took 20 min. in Access 2000, but now takes 6 hours in
Access 2003. The slow down seems to happen everytime I link to a created
table. For if I remake one query to not use a table, but look up the data, it
takes seconds instead of minutes.
I have made sure that any tables created are saved in the 2003 format.
I have tried Indexing and setting a Primary Key; no change
Does anyone know what might be slowing each query down, when it access a
'made' table?
Is there something I am missing during the conversion process? (I did delete
all the 'made tables' after the conversion)
I do not relish the idea of re-writting all the queries, since it would
entail making six different versions, one for each group that uses it.
Thanks
GW Hogg