D
Doug
Hi,
I've created a form that has 3 combo boxes on it and a graph.
The data source for each of the combo boxes is a query. Depending on what's
selected in the first one the possible results of the 2nd & 3rd are affected
because they use the subsequent selection value as a filter as a part of the
query. The graph that's generated is then shown as a result of each of the 3
options & so in turn, queries the query based on the 3 options as filters in
it's where clause...
The query isn't massive, runs quickly and the form's pretty quick to work
with. However, I get a serious problem with it increasing the size of my db
from 2.5mb to 22mb after using the form just a few times!!
Obviously, I can compact the database & get it back down to lower levels -
but I don't understand / know if there's anything I can do to stop this
massive (for me) build up in the size of my database (Access 2000).
Any help much appreciated.
I've created a form that has 3 combo boxes on it and a graph.
The data source for each of the combo boxes is a query. Depending on what's
selected in the first one the possible results of the 2nd & 3rd are affected
because they use the subsequent selection value as a filter as a part of the
query. The graph that's generated is then shown as a result of each of the 3
options & so in turn, queries the query based on the 3 options as filters in
it's where clause...
The query isn't massive, runs quickly and the form's pretty quick to work
with. However, I get a serious problem with it increasing the size of my db
from 2.5mb to 22mb after using the form just a few times!!
Obviously, I can compact the database & get it back down to lower levels -
but I don't understand / know if there's anything I can do to stop this
massive (for me) build up in the size of my database (Access 2000).
Any help much appreciated.