W
Water guy
I'm rather new to Access, but I'll try to explain my problem clearly.
I am using an EPA water quality modeling program known as WASP.
The WASP program can be set up to automatically import data from an Access
table.
In the WASP interface the user can then enter a query to limit the actually
imported data, thus speeding up processing time.
I have done this exact operation on many occasions and it seems to work great.
However, I have a very large database that I am seeking data from. In order
to aid in the process of finding the correct data and importing it into WASP,
I set up a make-table query to first limit the data set. (100,000 records to
45,000 records) Then I attempt to set the WASP program to automatically
import and query the new table. When I do this the WASP program locks up. I
am wondering if when I used a make-table query, the table produced had a
setting that limits the querying of that data. An suggestions?
I am also trying to find a problem on the side of the WASP model too.
Thanks,
Will
I am using an EPA water quality modeling program known as WASP.
The WASP program can be set up to automatically import data from an Access
table.
In the WASP interface the user can then enter a query to limit the actually
imported data, thus speeding up processing time.
I have done this exact operation on many occasions and it seems to work great.
However, I have a very large database that I am seeking data from. In order
to aid in the process of finding the correct data and importing it into WASP,
I set up a make-table query to first limit the data set. (100,000 records to
45,000 records) Then I attempt to set the WASP program to automatically
import and query the new table. When I do this the WASP program locks up. I
am wondering if when I used a make-table query, the table produced had a
setting that limits the querying of that data. An suggestions?
I am also trying to find a problem on the side of the WASP model too.
Thanks,
Will